Re: [4/4] RFC: implement catch load and catch unload

[Tom Tromey <tromey@redhat.com>]

>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:

Marc> Not having this command won't prevent CDI from debugging,
Marc> but will have two impacts, as far as I know:
Marc> 1- no more user feature to stop on lib events
Marc> 2- breakpoints set on non-loaded libs will no longer be
Marc> installed (since CDI does not use pending breakpoints, but
Marc> tries to plant failed bps at each new lib load event)

Just to be clear -- the command still exists and works.
What changed is how gdb reports it.  It used to be that you would get:

    -exec-continue
    ~"Stopped due to shared library event."
    *stopped

Now you will get:

    -exec-continue
    *stopped,reason="solib-event",[more stuff]

I can even restore the old output if you really need it; though I'd
prefer we just keep on with a more purely MI solution.

Tom