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

["Kris Warkentin" <kewarken@qnx.com>]

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?

cheers,

Kris

----- Original Message ----- 
From: "Andrew Cagney" <ac131313@redhat.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Sent: Tuesday, July 08, 2003 5:02 PM
Subject: Re: [rfc] Print solib events in mi-mode


> > 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)
>
>
>