Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kevin Buettner" <kevinb@redhat.com>,
	"Daniel Jacobowitz" <drow@mvista.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 17:49:00 -0000	[thread overview]
Message-ID: <093901c34642$884d0280$0202040a@catdog> (raw)
In-Reply-To: <1030709174134.ZM2191@localhost.localdomain>

> > > On Wed, Jul 09, 2003 at 11:39:26AM -0400, Kris Warkentin wrote:
> > > > > 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.
> > > >
> > > > What about solib-events on non-svr4 systems?  QNX is implementing
the
> > CDT
> > > > for Eclipse and we'd like to have equal functionality across
platforms.
> > >
> > > I picked on solib-svr4 because it's the one normally found lacking.
At
> > > least one of the solib backends already does this - probably SOM?
> >
> > So you're saying that you're not receptive to this patch but you'd
consider
> > a svr4 patch for the load catchpoints?
>
> If it could be moved out to solib.c, I'd be receptive to it.  I'm also
> willing to look at a patch which modifies solib-svr4.c, but I'd prefer
> one which handles all off the solib backends in one fell swoop.

The patch is for breakpoint.c.  It's in the print_it_typical() function
which handles output when a breakpoint is hit.  I'm not sure how I would put
this into solib.c.

cheers,

Kris



  reply	other threads:[~2003-07-09 17:49 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 [this message]
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='093901c34642$884d0280$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@redhat.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