GNU bug report logs - #10580
24.0.92; gdb initialization takes more than one minute at 100% CPU

Previous Next

Package: emacs;

Reported by: Dov Grobgeld <dov.grobgeld <at> gmail.com>

Date: Sun, 22 Jan 2012 17:55:03 UTC

Severity: important

Tags: patch

Found in version 24.0.92

Done: Stefan Monnier <monnier <at> iro.umontreal.ca>

Bug is archived. No further changes may be made.

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Chong Yidong <cyd <at> gnu.org>
Cc: dov.grobgeld <at> gmail.com, 10580 <at> debbugs.gnu.org
Subject: Re: bug#10580: 24.0.92;
	gdb initialization takes more than one minute at 100% CPU
Date: Tue, 08 May 2012 20:47:57 +0300

> From: Chong Yidong <cyd <at> gnu.org>
> Date: Wed, 09 May 2012 00:25:00 +0800
> Cc: 10580 <at> debbugs.gnu.org
> 
> Those are status messages from turning on GDB's MI (machine interface)
> system, I think, though I don't see why it makes so much difference in
> your case.
> 
> If you type, from the shell,
> 
>   gdb -i=mi YOUR-BINARY
>   r
> 
> do you similarly see a huge output?

As you know, in addition to "run", gdb-mi.el sends lots of other
commands behind the scenes, so the above is not a faithful simulation
of what happens when GDB is run by Emacs.  But I agree that if the
above produces similarly voluminous output, we cannot really blame
gdb-mi.el.
This bug report was last modified 12 years and 75 days ago.

Previous Next

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