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

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

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

> > 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.?

Kris