From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [03/19] set_longjmp_breakpoint
Date: Fri, 05 Jun 2009 22:00:00 -0000 [thread overview]
Message-ID: <m3oct2s5mg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200906052115.n55LF2H7027202@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Fri\, 5 Jun 2009 23\:15\:02 +0200 \(CEST\)")
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> As a side effect, if multiple objfiles provide longjmp, *all*
Ulrich> instances will now get the breakpoint installed -- this may actually
Ulrich> be useful in some circumstances (e.g. multiple SPE images in a Cell/B.E.
Ulrich> application).
This seems reasonable to me, but I am somewhat concerned about
performance. I think this patch means that every "next" will involve
looking up four symbols in every objfile.
Do you know how big an effect this has? Or maybe Paul could try it
on his famous kilo-.so program.
I suppose if that is very slow we could add some kind of per-inferior
cache.. ?
Tom
prev parent reply other threads:[~2009-06-05 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:15 Ulrich Weigand
2009-06-05 22:00 ` Tom Tromey [this message]
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=m3oct2s5mg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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