Re: [RFA]: Fix for pending breakpoints in manually loaded/unloadedshlibs

[Andrew Cagney <cagney at gnu dot org>]

> > Date: Thu, 12 Aug 2004 08:10:28 -0400
> > > From: Andrew Cagney <cagney@gnu.org>
> >
> > > > > 
> > > > > But we don't want to _monitor_ anything in this case.  We want to fox
> > > > > a specific, well-defined problem due to a specific course of events.
> >
> > > And that well defined course of events is called an shlib unload.  Lets 
> > > abstract it as such.
>
>
> Sorry, this is too terse for me to follow.  I'd appreciate if you
> could elaborate a bit.

Here's a reference http://patterndigest.com/patterns/Observer.html
For our case the RealSubject is an shlib-unload.  solib.c doesn't need 
to know who is interested in this, just that there is something. 
Conversely, the breakpoint code, doesn't care about the course of events 
that lead to an shlib-unload, just that it occured.

Andrew