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

Previous Next

Full log

View this message in rfc822 format

From: Dov Grobgeld <dov.grobgeld <at> gmail.com>
To: Chong Yidong <cyd <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 10580 <at> debbugs.gnu.org, schwab <at> linux-m68k.org
Subject: bug#10580: 24.0.92; gdb initialization takes more than one minute at 100% CPU
Date: Thu, 10 May 2012 22:07:38 +0300

[Message part 1 (text/plain, inline)]

Here are the tests when using the the latest cvs gdb that yields a gdb
output file of about 800k.

Without gdb-get-source-file-list override: ~139s
With gdb-get-source-file-list override: ~125s

Thus it is clear that most of the time is taken just reading the string
into emacs. But doing find-file on the same file is almost instantaneous.

Regards,
Dov


On Thu, May 10, 2012 at 5:13 PM, Chong Yidong <cyd <at> gnu.org> wrote:

> Dov Grobgeld <dov.grobgeld <at> gmail.com> writes:
>
> > Still, it bothering me the fact that the above perl expression parses
> > the gdb output in a fraction of a second, (0.01s user time) whereas
> > gdb-mi.el takes more than 40s.
>
> I would also like to learn more about where the bottleneck is.
>
> Could you do the following:
>
> M-: (require 'gdb-mi) RET
> M-: (defun gdb-get-source-file-list () nil) RET
>
> then run M-x gdb as usual, and see if that makes any difference in
> performance?  Leave gdb-create-source-file-list set at t.
>
> (The above steps cause gdb-mi to issue the -file-list-exec-source-files
> command and read the output, as usual, but skip parsing the output into
> the source file list.)
>

[Message part 2 (text/html, inline)]

Previous Next

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