From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Andrew Cagney <ac131313@redhat.com>,
"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [rfc] Print solib events in mi-mode
Date: Wed, 09 Jul 2003 15:09:00 -0000 [thread overview]
Message-ID: <20030709150847.GA19020@nevyn.them.org> (raw)
In-Reply-To: <064e01c34615$0b152ae0$0202040a@catdog>
On Wed, Jul 09, 2003 at 08:24:28AM -0400, Kris Warkentin wrote:
> Actually, I had looked at those and some other related threads. I suggested
> to our Eclipse guys that it would probably be easy for them to just
> implement it in the IDE (since all the apps and libs are already projects
> under IDE control) using the stop-on-solib-event mechanism. They countered
> that there was no mi feedback on whether an stop was solib related, hence my
> patch.
>
> If there's no objection to the output this provides, I wouldn't mind
> applying it. MI-ification is generally a good thing right? Is there
> somewhere I should document this as well?
TBH, I'd rather see load catchpoints implemented and MI-ified for
solib-svr4.c. The natural implementation returns more useful
information, namely what libraries were loaded or unloaded. It should
be easy but it's never trickled to the top of anyone's TODO.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-09 15:09 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
2003-07-09 12:24 ` Kris Warkentin
2003-07-09 15:09 ` Daniel Jacobowitz [this message]
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=20030709150847.GA19020@nevyn.them.org \
--to=drow@mvista.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).