help-gnu-emacs
[Top][All Lists]
Advanced

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

Re: gud : Phase error in gdb-pre-prompt (got pre-emacs)


From: Francis Moreau
Subject: Re: gud : Phase error in gdb-pre-prompt (got pre-emacs)
Date: Mon, 30 Jun 2008 13:37:52 +0200

Hello,

On Fri, Jun 27, 2008 at 12:18 PM, Nick Roberts <address@hidden> wrote:
>  > I'm not lucky with my switch from emacs21 to GNU Emacs 22.2.1
>  > (i686-pc-linux-gnu, GTK+ Version 2.8.20): first emacs still hangs on
>  > (next-buffer) (see earlier posting...), now gud is not working.
>  >
>  > What I did:
>  >
>  > >M-x gdb
>  > >gdb --annotate=3 binary.bin
>  >
>  > gdb loads the binary, I get the gdb prompt. Then:
>  >
>  > Current directory is somewhere.
>  > GNU gdb 6.6
>  > Copyright (C) 2006 Free Software Foundation, Inc. [...]
>  > This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db
>  > library "/lib/tls/i686/cmov/libthread_db.so.1".
>  > (gdb) run
>  >   C-c C-c  C-c C-c  C-c C-c
>  >
>  >   C-c C-c
>  >   C-c C-c  C-c C-c
>

I have a similar behaviour except that once the file is loaded emacs says
within the square brackets:

    [Initializing...]

forever. I need to do 'run', C-c Cc, <wait for ~10 seconds>. After that emacs
says

    [ready]

If I simply do 'run', emacs only show [Initializing...] forever.

>
> There are several factors that might make this slow:
>
> 1) An executable that was created from a large number of files.

That's probably is the case since I'm loading Linux kernel.

> 2) Using stabs debug format.

I don't

> 3) Using an old PC.

I don't

>
> If this is the problem I can post a patch that might speed things up but
> just turning off gud-tooltip-mode might help.
>

turning off gud-tooltip-mode doesn't help.

> If you still get an error after waiting for "ready":
>
> 1) Set gdb-enable-debug to t using M-x set-variable.
> 2) Do M-x gdb and enter "run" in the GUD buffer to get the error.
> 4) Post the value of gdb-debug-log (you can use `C-h v') to the list
>  (or just to me if it's large).

Here it is:

gdb-debug-log is a variable defined in `gdb-ui.el'.
Its value is
((recv . "\n^Z^Zpre-prompt\n(gdb) \n^Z^Zprompt\n")
 (recv . 
"\n^Z^Zpost-prompt\n^done,frame={level=\"0\",addr=\"0x84002000\",func=\"_stext\"}\n(gdb)
\n")
 (send-item "server interpreter mi -stack-info-frame\n" gdb-get-version))


thanks,
-- 
Francis




reply via email to

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