From: Gary Benson <gbenson@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: hacky fix for PR 12406
Date: Fri, 13 Jan 2012 15:48:00 -0000 [thread overview]
Message-ID: <20120113154634.GA9257@redhat.com> (raw)
In-Reply-To: <m3fwfkzk0i.fsf@fleche.redhat.com>
Tom Tromey wrote:
> >>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>
> Joel> An idea that crossed my mind: Add a flag to each entry in our
> Joel> SO list. Everytime we stop, we use that flag to determine
> Joel> which entries are new. We can probably use something like the
> Joel> normal-stop hook to set the flag just before giving the prompt
> Joel> back to the user. Would that work? It would support the
> Joel> situation I mentioned above where we get one breakpoint event
> Joel> for multiple shared libraries...
>
> Thanks for the idea. I will give it a try.
>
> Tom> [Inferior loaded library /lib64/ld-linux-x86-64.so.2]
> Tom> Stopped due to shared library event
>
> Gary> Could this be a separate option, trace-solib-events maybe?
> Gary> It seems like this printing might also be useful when
> Gary> stop-on-solib-events is off.
>
> Gary> Also, as Jan said, it would be nice to have unload
> Gary> notifications too.
>
> This comment inspired me to take another look at the whole problem.
>
> I actually do not much like stop-on-solib-events. I think 'catch'
> commands are better, because they offer the user more control:
> commands at the stop point, "silent", conditions.
>
> So now I am thinking that, while I may still add the notification in
> some form, I will also resurrect "catch load" and "catch unload",
> something like "catch load [REGEX] [if ...]"
Sounds nice!
Cheers,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2012-01-13 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 19:25 Tom Tromey
2012-01-12 0:12 ` Jan Kratochvil
2012-01-12 5:59 ` Joel Brobecker
2012-01-12 21:41 ` Tom Tromey
2012-01-13 15:48 ` Gary Benson [this message]
2012-01-12 11:40 ` Gary Benson
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=20120113154634.GA9257@redhat.com \
--to=gbenson@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).