GNU bug report logs - #3585
gdb not responding on Emacs from CVS

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 3585 in the body.
You can then email your comments to 3585 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Baoqiu Cui <cbaoqiu <at> yahoo.com>
To: gnu-emacs-bug <at> moderators.isc.org
Subject: gdb not responding on Emacs from CVS
Date: Mon, 15 Jun 2009 19:57:02 -0700

Hi,

I've had this problem for a while on Emacs built from CVS.  Today I
updated my Emacs directory and rebuilt everything, the problem still
exists (GNU Emacs 23.0.94.1 (x86_64-unknown-linux-gnu, X toolkit)).

Basically, after typing in ``M-x gdb'' to debug a program, say myprog, a
buffer called *gud-myprog* will appear, and it displays some info about
gdb and prints out a prompt:

  (gdb) _

Now, if I type in a command like "pwd" and press Enter, *nothing*
happens.  I have to press C-c C-c to get out:

  (gdb) pwd
    C-c C-cQuit
  (gdb)

This does not happen on Emacs 22.3.

Does anyone know what the problem is?

Thanks,
Baoqiu

Message #10 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: nickrob <at> snap.net.nz (Nick Roberts)
To: Baoqiu Cui <cbaoqiu <at> yahoo.com>, 3585 <at> debbugs.gnu.org
Cc: gnu-emacs-bug <at> moderators.isc.org
Subject: bug#3585: gdb not responding on Emacs from CVS
Date: Wed, 17 Jun 2009 00:58:33 +1200

Baoqiu Cui writes:
 > Hi,
 > 
 > I've had this problem for a while on Emacs built from CVS.  Today I
 > updated my Emacs directory and rebuilt everything, the problem still
 > exists (GNU Emacs 23.0.94.1 (x86_64-unknown-linux-gnu, X toolkit)).
 > 
 > Basically, after typing in ``M-x gdb'' to debug a program, say myprog, a
 > buffer called *gud-myprog* will appear, and it displays some info about
 > gdb and prints out a prompt:
 > 
 >   (gdb) _
 > 
 > Now, if I type in a command like "pwd" and press Enter, *nothing*
 > happens.  I have to press C-c C-c to get out:
 > 
 >   (gdb) pwd
 >     C-c C-cQuit
 >   (gdb)
 > 
 > This does not happen on Emacs 22.3.
 > 
 > Does anyone know what the problem is?

I don't see this.  What version of GDB do you have?

Can you please do M-x gdb-enable-debug before M-x gdb and post the value of gdb-debug-log
after doing:

(gdb) pwd<RET>

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Message #20 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Baoqiu Cui <cbaoqiu <at> yahoo.com>
To: gnu-emacs-bug <at> moderators.isc.org
Subject: Re: bug#3585: gdb not responding on Emacs from CVS
Date: Tue, 16 Jun 2009 10:00:01 -0700

Thanks for looking into this, Nick.  Please the info you need below:

nickrob <at> snap.net.nz (Nick Roberts) writes:

> Baoqiu Cui writes:
>  > Hi,
>  > 
>  > I've had this problem for a while on Emacs built from CVS.  Today I
>  > updated my Emacs directory and rebuilt everything, the problem still
>  > exists (GNU Emacs 23.0.94.1 (x86_64-unknown-linux-gnu, X toolkit)).
>  > 
>  > Basically, after typing in ``M-x gdb'' to debug a program, say myprog, a
>  > buffer called *gud-myprog* will appear, and it displays some info about
>  > gdb and prints out a prompt:
>  > 
>  >   (gdb) _
>  > 
>  > Now, if I type in a command like "pwd" and press Enter, *nothing*
>  > happens.  I have to press C-c C-c to get out:
>  > 
>  >   (gdb) pwd
>  >     C-c C-cQuit
>  >   (gdb)
>  > 
>  > This does not happen on Emacs 22.3.
>  > 
>  > Does anyone know what the problem is?
>
> I don't see this.  What version of GDB do you have?
>
> Can you please do M-x gdb-enable-debug before M-x gdb and post the value of gdb-debug-log
> after doing:
>
> (gdb) pwd<RET>

After typing in ``pwd<RET>'', gdb-debug-log has the following value
(from which you can see the GDB version that I use):

------------------------------------------------------------------------
gdb-debug-log is a variable defined in `gdb-ui.el'.
Its value is 
((recv . "(gdb) ")
 (recv . "Using host libthread_db library \"/lib64/tls/libthread_db.so.1\".\n")
 (recv . "License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\nThis GDB was configured as \"x86_64-unknown-linux-gnu\"...\n")
 (recv . "GNU gdb 6.7.1\nCopyright (C) 2007 Free Software Foundation, Inc.\n"))
------------------------------------------------------------------------

It seems that the Return key was ignored.  After pressing C-c C-c, the
value of gdb-debug-log becomes:

------------------------------------------------------------------------
gdb-debug-log is a variable defined in `gdb-ui.el'.
Its value is 
((recv . "(gdb) ")
 (recv . "Quit\n")
 (recv . "(gdb) ")
 (recv . "Using host libthread_db library \"/lib64/tls/libthread_db.so.1\".\n")
 (recv . "License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\nThis GDB was configured as \"x86_64-unknown-linux-gnu\"...\n")
 (recv . "GNU gdb 6.7.1\nCopyright (C) 2007 Free Software Foundation, Inc.\n"))
------------------------------------------------------------------------

Thanks,
Baoqiu

Message #25 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Baoqiu Cui <cbaoqiu <at> yahoo.com>
To: gnu-emacs-bug <at> moderators.isc.org
Subject: Re: bug#3585: gdb not responding on Emacs from CVS
Date: Tue, 16 Jun 2009 14:40:13 -0700

Baoqiu Cui <cbaoqiu <at> yahoo.com> writes:

> After typing in ``pwd<RET>'', gdb-debug-log has the following value
> (from which you can see the GDB version that I use):
>
> ------------------------------------------------------------------------
> gdb-debug-log is a variable defined in `gdb-ui.el'.
> Its value is 
> ((recv . "(gdb) ")
>  (recv . "Using host libthread_db library \"/lib64/tls/libthread_db.so.1\".\n")
>  (recv . "License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\nThis GDB was configured as \"x86_64-unknown-linux-gnu\"...\n")
>  (recv . "GNU gdb 6.7.1\nCopyright (C) 2007 Free Software Foundation, Inc.\n"))
> ------------------------------------------------------------------------
>
> It seems that the Return key was ignored.  After pressing C-c C-c, the
> value of gdb-debug-log becomes:
>
> ------------------------------------------------------------------------
> gdb-debug-log is a variable defined in `gdb-ui.el'.
> Its value is 
> ((recv . "(gdb) ")
>  (recv . "Quit\n")
>  (recv . "(gdb) ")
>  (recv . "Using host libthread_db library \"/lib64/tls/libthread_db.so.1\".\n")
>  (recv . "License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\nThis GDB was configured as \"x86_64-unknown-linux-gnu\"...\n")
>  (recv . "GNU gdb 6.7.1\nCopyright (C) 2007 Free Software Foundation, Inc.\n"))
> ------------------------------------------------------------------------

Here is some more information.  It seems that this problem has something
to do with the size of the program that I am trying to debug.  If I try
to follow the same steps for a small testing program, everything is
fine.

I noticed that, for the big program that I was debugging, it took about
50 seconds to have the "[initializing...]" Debugger status in mode-line
changed to "[ready]".  GDB simply does not respond to user's commands
before it is *ready*.

I tried the same thing on Emacs 21, which does not report status like
[initializing...] or [ready], and it seems that GDB interface there is
much faster.  It only takes 10-15 seconds to load the same big program
and then display the "(gdb) " prompt.  Once the prompt is displayed, GDB
is *ready* to respond any command I type in.

Why does it take 50 seconds to "initialize" things?  Emacs 22 seems to
have the same "delay".  Is there anyway to cut the time spent on
initializing?

Thanks,
Baoqiu

Message #30 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: nickrob <at> snap.net.nz (Nick Roberts)
To: Baoqiu Cui <cbaoqiu <at> yahoo.com>, 3585 <at> debbugs.gnu.org
Cc: gnu-emacs-bug <at> moderators.isc.org
Subject: bug#3585: gdb not responding on Emacs from CVS
Date: Mon, 22 Jun 2009 00:47:51 +1200

 > Here is some more information.  It seems that this problem has something
 > to do with the size of the program that I am trying to debug.  If I try
 > to follow the same steps for a small testing program, everything is
 > fine.
 > 
 > I noticed that, for the big program that I was debugging, it took about
 > 50 seconds to have the "[initializing...]" Debugger status in mode-line
 > changed to "[ready]".  GDB simply does not respond to user's commands
 > before it is *ready*.
 > 
 > I tried the same thing on Emacs 21, which does not report status like
 > [initializing...] or [ready], and it seems that GDB interface there is
 > much faster.  It only takes 10-15 seconds to load the same big program
 > and then display the "(gdb) " prompt.  Once the prompt is displayed, GDB
 > is *ready* to respond any command I type in.
 > 
 > Why does it take 50 seconds to "initialize" things?  Emacs 22 seems to
 > have the same "delay".  Is there anyway to cut the time spent on
 > initializing?

Emacs 22 builds a list of filenames from GDB that were used to build the
executable and this takes a long time if you have an executable that was
created from a large number of files, particularly if you use stabs debug
format.  There is an option, gdb-create-source-file-list, which when set to
nil means that Emacs doesn't build this list at start up.  That makes it
quicker but if there are relevant files in existing buffers or you visit them
they won't be enabled for debugging, e.g., you won't be able to click in the
fringe to set a breakpoint until execution has already stopped there.

This option has been around since 2008-07-01.  If your Emacs predates this then
you might like to get Emacs 23.1 which will be released shortly.

Alternatively you can get the Emacs 21 speed/behavior by using M-x gud-gdb.


-- 
Nick                                           http://www.inet.net.nz/~nickrob

Message #40 received at 3585 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Pranith Kumar <bobby.prani <at> gmail.com>
To: 3585 <at> debbugs.gnu.org
Subject: Still contains it
Date: Tue, 29 Sep 2009 17:32:49 +0530

Hello,

I am using the released emacs 23.1 source and this still contains the bug.

Using M-x gud-gdb solves the problem.

Thanks,
-- 
Pranith.

Message #45 received at 3585 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Pranith Kumar <bobby.prani <at> gmail.com>
Cc: 3585 <at> debbugs.gnu.org
Subject: Re: Still contains it
Date: Sat, 17 Sep 2011 08:07:10 +0200

Pranith Kumar <bobby.prani <at> gmail.com> writes:

> I am using the released emacs 23.1 source and this still contains the bug.
>
> Using M-x gud-gdb solves the problem.

This was marked as wontfix + notabug without any explanation, but not
closed, so I'm wondering whether you're still seeing this bug in Emacs
24?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Message #50 received at 3585 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Pranith Kumar <bobby.prani <at> gmail.com>
Cc: 3585 <at> debbugs.gnu.org
Subject: Re: bug#3585: Still contains it
Date: Fri, 07 Oct 2011 00:08:15 +0200

Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:

>> I am using the released emacs 23.1 source and this still contains the bug.
>>
>> Using M-x gud-gdb solves the problem.
>
> This was marked as wontfix + notabug without any explanation, but not
> closed, so I'm wondering whether you're still seeing this bug in Emacs
> 24?

More information was requested, but was apparently not given, so I'm
closing this bug report.  If this is still a problem, please reopen this
bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.