From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [rfc] Print solib events in mi-mode
Date: Tue, 08 Jul 2003 21:02:00 -0000 [thread overview]
Message-ID: <3F0B315E.7000702@redhat.com> (raw)
In-Reply-To: <062401c34590$97cd09b0$0202040a@catdog>
> What do you think of something like this? When stop-on-solib-events is set,
> this will print the reason as being a shared-lib-event.
>
> Our Eclipse team wants to be able to set breakpoints in shared libraries
> that aren't loaded yet. If they get notification of shlib-events, then they
> can re-examine the list of loaded libraries and set any breakpoints that
> have been enabled in the project's libs.
See: [RFC] add 'save-breakpoints' command
http://sources.redhat.com/ml/gdb-patches/2001-12/threads.html#00114
(but check for other related threads).
The resolution was interesting, instead of adding a new command, modify
the existing command so that it would add breakpoints that would be
automatically enabled later.
Andrew
(although the patch is probably also useful)
next prev parent reply other threads:[~2003-07-08 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:35 Kris Warkentin
2003-07-08 21:02 ` Andrew Cagney [this message]
2003-07-09 12:24 ` Kris Warkentin
2003-07-09 15:09 ` Daniel Jacobowitz
2003-07-09 15:38 ` Kris Warkentin
2003-07-09 16:24 ` Daniel Jacobowitz
2003-07-09 17:29 ` Kris Warkentin
2003-07-09 17:41 ` Kevin Buettner
2003-07-09 17:49 ` Kris Warkentin
2003-07-09 18:01 ` Kris Warkentin
2003-07-09 18:05 ` Daniel Jacobowitz
2003-07-09 18:21 ` Kris Warkentin
2003-07-09 18:30 ` Daniel Jacobowitz
2003-07-09 19:12 ` Kris Warkentin
2003-07-09 19:46 ` Daniel Jacobowitz
2003-07-09 20:00 ` Kris Warkentin
2003-07-09 20:03 ` Daniel Jacobowitz
2003-07-18 16:12 ` Andrew Cagney
2003-07-09 20:38 ` Jason Molenda
2003-07-10 12:23 ` Kris Warkentin
2003-07-10 16:33 ` Andrew Cagney
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=3F0B315E.7000702@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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