From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Improve performance with lots of shared libraries
Date: Fri, 09 Sep 2011 14:51:00 -0000 [thread overview]
Message-ID: <20110909143521.GA12299@host1.jankratochvil.net> (raw)
In-Reply-To: <CAN9gPaGBi=HxTzNjk7T_6oivHx8vO4XrXKk1F9fRACWERK=qVw@mail.gmail.com>
On Fri, 09 Sep 2011 16:25:30 +0200, Daniel Jacobowitz wrote:
> On Fri, Sep 9, 2011 at 8:31 AM, Gary Benson <gbenson@redhat.com> wrote:
> > Â * when there are no pending breakpoints,
>
> If you "break foo", it might put that breakpoint in more than one
> shared library. If you load a new library with an implementation of
> foo, we should stop on that one too. How can we make that work
> without processing the library events?
This feature was planned being aware of this problem.
It does not work currently, GDB just puts the breakpoint on a random first
place found.
The Tom's multi-location breakpoints patch (archer-tromey-ambiguous-linespec)
is being coded with this behavior so that by default gdb syntax it is defined
the first resolution is final.
http://sourceware.org/ml/gdb-patches/2011-07/msg00740.html
I would guess this patch should be checked-in only after Tom's. Or make it
opt-in configurable. Or just say the already broken behavior is now broken in
a different way.
Thanks,
Jan
next prev parent reply other threads:[~2011-09-09 14:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:25 Gary Benson
2011-09-09 14:35 ` Daniel Jacobowitz
2011-09-09 14:51 ` Jan Kratochvil [this message]
2011-09-09 15:04 ` Pedro Alves
2011-09-09 19:41 ` Jan Kratochvil
2011-09-12 12:44 ` Pedro Alves
2011-09-12 16:44 ` Jan Kratochvil
2011-09-14 9:28 ` Gary Benson
2011-10-04 19:46 ` Tom Tromey
2011-09-09 15:11 ` Pedro Alves
2011-09-09 14:53 ` Jan Kratochvil
2011-10-04 20:03 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2011-09-22 17:35 Gary Benson
2011-07-01 16:51 Gary Benson
2011-07-01 17:19 ` Tom Tromey
2011-07-04 14:10 ` Gary Benson
2011-07-01 17:32 ` Joel Brobecker
2011-07-04 14:21 ` Gary Benson
2011-07-01 17:45 ` Pedro Alves
2011-07-01 17:57 ` Pedro Alves
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=20110909143521.GA12299@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox