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

[Daniel Jacobowitz <drow@mvista.com>]

On Wed, Jul 09, 2003 at 04:00:52PM -0400, Kris Warkentin wrote:
> > > The other is just to compare against a dll_pathname so we could get away
> > > with creating a SOLIB_WAS_(UN)LOADED(pid, "libname") and have the
> backend
> > > check through the list for libname.
> >
> > Sure.  Or return a list and let solib.c sort between 'em.
> 
> Do you think these functions should be in current_target_so_ops?

Hmm... yes, probably.

> > > Okay...that seems reasonable.  Another question: since we've already got
> a
> > > solib breakpoint set in svr4, we don't need to call
> > > create_solib_load_event_breakpoint() like somsolib.c and pa64solib.c do.
> > > Can you have multiple types associated with a single break or do we just
> set
> > > another at the same address?
> >
> > It should be multiple "catchpoints", and inserting catchpoints would do
> > nothing to the target.  This may require violence to the breakpoint
> > system, which is why I haven't done it yet :(
> 
> You're suggesting a list of gdb "actions" associated with a single
> breakpoint on the target? IE, test for a condition, execute a catch, check
> solibs on the target, etc.?

No, a set of catchpoints (type bp_catch_load), one for each condition. 
But inserting or removing them would do nothing on svr4; the breakpoint
is always inserted.  When we hit that breakpoint we would check for all
catch_load and catch_unloads.

This is part of the needed breakpoint overhaul.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer