Re: [rfc] Print solib events in mi-mode

[Daniel Jacobowitz <drow at mvista dot com>]

On Wed, Jul 09, 2003 at 11:39:26AM -0400, Kris Warkentin wrote:
> > 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.
> 
> 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?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer