[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs fails parsing gdb output

From: Johan Walles
Subject: Re: Emacs fails parsing gdb output
Date: Thu, 12 Jul 2007 14:26:52 +0200

Using gdba rather than gdb is a good enough workaround for us.  Thanks!

Apart from that I've attempted to answer your questions inline below.

2007/7/12, Nick Roberts <address@hidden>:

> In GNU Emacs (i486-pc-linux-gnu, GTK+ Version 2.10.11)
>  of 2007-07-06 on helios

I have GNU gdb 6.6-debian and it works fine with GNU Emacs
(i686-pc-linux-gnu, GTK+ Version 2.10.11).

It works with small test cases, but fails on our big ugly real-world case.

> > then post the value of gdb-debug-log to address@hidden

> Attached.

This log looks OK but it's prior to execution.

Actually the run I gave you was with the scripts being run, so the
program has actually started running and hit some breakpoints.  The
first problem we get is that the lower (source code pane) doesn't
open, but that may or may not be logged in any way.

I'm attaching a new debug log where I've gone one step further and
done "f" in the GDB pane to get the source window to refresh.  That
did get me a bunch of error messages which might make this log a bit
more interesting to you.

What happens if you start your application under GDB without the GDB

The reason we have the scripts is that what we're debugging is a
library (libjvm.so), and the scripts run load and run things long
enough for us to get into our library.  If we don't run the scripts,
nothing will even get loaded into gdb.

I think that M-x gdb doesn't work in you start execution from within a script.
In this case you must use M-x gdba.  Does this work?

Yes!  What's the difference betweeen gdb and gdba?  I wasn't able to
find anything documenting the difference, according to the docs they
seem to do roughly the same thing.

Attachment: gdb-debug-log2.txt
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]