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

View this message in rfc822 format

From: Chong Yidong <cyd <at> gnu.org>
To: Dov Grobgeld <dov.grobgeld <at> gmail.com>
Cc: 10580 <at> debbugs.gnu.org
Subject: bug#10580: 24.0.92; gdb initialization takes more than one minute at 100% CPU
Date: Wed, 09 May 2012 00:25:00 +0800

Dov Grobgeld <dov.grobgeld <at> gmail.com> writes:

> Indeed, my result is much fatter.
>
> (safe-length gdb-debug-log) => 223
>
> and the total length of the messages is about 800k. So it seems that
> the time spent is simply the parsing of this large chunk of data? What
> gdb command is run that outputs all the file="..." commands?

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?
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.