Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Accelerate blocks sorting
Date: Mon, 22 Jun 2009 18:26:00 -0000	[thread overview]
Message-ID: <20090622182617.GA30367@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4A3FCA0A.3020403@vmware.com>

On Mon, 22 Jun 2009 20:14:34 +0200, Michael Snyder wrote:
> Jan Kratochvil wrote:
>> GDB has been reported as hanging on crashed webkit.
>> https://bugzilla.redhat.com/show_bug.cgi?id=507267
>>
>> Time of (using webkitgtk-debuginfo-1.1.8-1.fc11.x86_64)
>> 	gdb -nx -ex 'info line *0x350080' ~/t/libwebkit-1.0.so.2.6.0.debug </dev/null
>>
>> the patch reduces from 40.1s to 4.6s.  (0x350080 is in a CU of 0x8d6ed bytes.)


> Is it actually hanging?  Or is it just taking a long time?
[...]
> but I'm a little confused about the problem being fixed.

I do not know, provided updated GDB to the bugreporter, he may respond.

This patch may be completely unrelated to the bugreport.  Nonetheless it can
be proven by my testcase it improves the performance in specific cases a lot.

(I believe it should make this libwebkit case acceptably slow - as GDB
currently is already slow while reading debug info in general.)


> The patch looks ok at first glance,

Thanks for the review but not sure if it was a check-in approval.


Thanks,
Jan


  reply	other threads:[~2009-06-22 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 17:39 Jan Kratochvil
2009-06-22 18:15 ` Michael Snyder
2009-06-22 18:26   ` Jan Kratochvil [this message]
2009-06-22 18:26 ` Tom Tromey
2009-06-22 18:35   ` Jan Kratochvil
2009-06-22 19:26     ` Tom Tromey
2009-06-22 19:51       ` Jan Kratochvil

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090622182617.GA30367@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox