emacs-pretest-bug
[Top][All Lists]
Advanced

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

Re: Using gdb in emacs 21 on Mac OS X 10.1.5


From: peter . ilberg
Subject: Re: Using gdb in emacs 21 on Mac OS X 10.1.5
Date: Wed, 1 Sep 2004 07:07:38 -0500

Nick Roberts <address@hidden> wrote on 08/29/2004 07:35:12 AM:
> I have no access to CVS Emacs at the moment and won't have for the next 
month
> In any case I don't have a Mac. So if you can debug the problem that
> would be great.
> The above thread talks about a lisp variable called (something like)
> gdb-enable-debug-log.
> If you set that and evauate gdb-debug-log, it might help you.
> 
> > Also, running gdb with or without --annotate=3 didn't change anything
> > except for all the annotations cluttering my gdb buffer.
> 
> What version of gdb are you using?

I'm using gdb 5.0 (20001113 Apple version 203 built on 11-07-2001).

After playing around with it for some time I found one problem at least.
gud-gdb-massage-args isn't defined anymore. This function used to append
"-fullname" to the command-line arguments for gdb. With the option
source file locations are given as

/somewhere/in/my/home/directory/file.c

Without the option source file locations are indicated by gdb as

source /somewhere/in/my/home/directory/file.c

And the additional "source " throws gud.el off.

With this fixed

M-x gdb with  gdb ./test               works as expected
M-x gdb with  gdb --annotate=3 ./test  doesn't work ie. no source buffer
                                       but lots of annotations in 
*gud-main*
M-x gdba with gdb --annotate=3 ./test  hangs on first user input in 
*gud-main*
                                                   and no source buffer
                                                   "hang" means nothing 
happens no matter
                                       what I type into *gud-main*

I've looked at gdb-debug-log in the gdba case. Emacs apparently only 
receives
gdb's startup message/version/warranty/copyright and the first prompt. 
Nothing
else is in the log. I'll try to look at it again, but it'll probably take 
me
a while to find the time.

Peter




reply via email to

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