From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
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 18:05:00 -0000 [thread overview]
Message-ID: <20030709180553.GA23828@nevyn.them.org> (raw)
In-Reply-To: <095501c34644$31dec7b0$0202040a@catdog>
On Wed, Jul 09, 2003 at 02:02:00PM -0400, Kris Warkentin wrote:
> Someone just pointed something out to me. "set stop-on-solib-events 1" is
> NOT enable-load-catchpoint or anything else. Yes, those things should exist
> for all solib platforms but the bottom line is that stop-on-solib-events is
> not currently mi-enabled and it should be.
>
> I want to make that command result in proper mi output, regardless of any
> other things which might be implemented in the future.
And I want load catchpoints fixed, so that stop-on-solib-events is
NEVER MI-enabled, so that it can be removed instead of supported for
years. It is in every way inferior to catchpoints. That was my point.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-09 18:05 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
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 [this message]
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=20030709180553.GA23828@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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).