From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: 10580@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#10580: 24.0.92; gdb initialization takes more than one minute at 100% CPU
Date: Fri, 11 May 2012 11:29:57 +0300 [thread overview]
Message-ID: <CA++fsGFh9CTqZLxc1YipXVfTVuVkNg3xgv38otu7DFrQoPkeRA@mail.gmail.com> (raw)
In-Reply-To: <8762c3z0of.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Here are the results.
With patch1: ~155s
With patch2: ~112s
On the other hand, I have patched gdb, seehttp://
sourceware.org/bugzilla/show_bug.cgi?id=14081, to do uniq internally in
gdb, and then it takes only about 10s.
On Fri, May 11, 2012 at 9:33 AM, Chong Yidong <cyd@gnu.org> wrote:
> Dov Grobgeld <dov.grobgeld@gmail.com> writes:
>
> > 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.
>
> Here's another little experiment. Could you apply the two attached
> patches, individually, and see what difference each patch makes?
> (Again, with gdb-create-source-file-list at its default of t, and
> without any other patches to gdb-mi.el.)
>
>
[-- Attachment #2: Type: text/html, Size: 1558 bytes --]
next prev parent reply other threads:[~2012-05-11 8:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 12:42 bug#10580: 24.0.92; gdb initialization takes more than one minute at 100% CPU Dov Grobgeld
2012-01-23 0:53 ` Glenn Morris
[not found] ` <CA++fsGG4YuTtb2VC9R+GRcPN5+JSaKpkb+uO3WAX0+VXmh8HDQ@mail.gmail.com>
2012-01-23 9:21 ` Glenn Morris
2012-01-25 0:37 ` Glenn Morris
2012-01-25 8:49 ` Dov Grobgeld
2012-01-25 9:39 ` Dov Grobgeld
2012-01-25 19:05 ` Glenn Morris
2012-04-30 5:33 ` Dov Grobgeld
2012-04-30 6:36 ` Dov Grobgeld
2012-05-06 4:13 ` Chong Yidong
2012-05-06 4:55 ` Dov Grobgeld
2012-05-06 5:39 ` Chong Yidong
2012-05-06 7:06 ` Dov Grobgeld
2012-05-07 2:53 ` Chong Yidong
2012-05-07 5:07 ` Dov Grobgeld
2012-05-07 6:11 ` Chong Yidong
2012-05-07 6:26 ` Chong Yidong
2012-05-08 5:33 ` Dov Grobgeld
2012-05-08 7:56 ` Dov Grobgeld
2012-05-08 8:28 ` Chong Yidong
2012-05-08 11:59 ` Dov Grobgeld
2012-05-08 16:25 ` Chong Yidong
2012-05-08 17:47 ` Eli Zaretskii
2012-05-08 21:07 ` Dov Grobgeld
2012-05-08 21:24 ` Andreas Schwab
2012-05-08 21:30 ` Dov Grobgeld
2012-05-09 7:47 ` Andreas Schwab
2012-05-09 8:44 ` Dov Grobgeld
2012-05-09 17:36 ` Eli Zaretskii
2012-05-10 6:00 ` Dov Grobgeld
2012-05-10 14:13 ` Chong Yidong
2012-05-10 19:07 ` Dov Grobgeld
2012-05-10 20:25 ` Stefan Monnier
2012-05-11 6:33 ` Chong Yidong
2012-05-11 8:29 ` Dov Grobgeld [this message]
2012-05-11 9:47 ` Eli Zaretskii
2012-05-11 13:27 ` Chong Yidong
2012-11-05 20:36 ` Dov Grobgeld
2012-11-05 20:46 ` Eli Zaretskii
2012-11-05 23:51 ` Stefan Monnier
2012-05-10 16:32 ` Eli Zaretskii
2012-05-10 18:43 ` Dov Grobgeld
2012-05-08 17:38 ` Eli Zaretskii
2012-12-14 4:14 ` bug#10580: 24.0.92; gdb initialization takes more than one minute at 100 Jean-Philippe Gravel
2012-12-18 4:45 ` Jean-Philippe Gravel
2012-12-21 4:01 ` Chong Yidong
2013-03-01 3:31 ` Jean-Philippe Gravel
2013-03-11 17:14 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA++fsGFh9CTqZLxc1YipXVfTVuVkNg3xgv38otu7DFrQoPkeRA@mail.gmail.com \
--to=dov.grobgeld@gmail.com \
--cc=10580@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).