From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6315 invoked by alias); 12 Aug 2004 20:44:51 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6307 invoked from network); 12 Aug 2004 20:44:50 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 12 Aug 2004 20:44:50 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i7CKiie3028442 for ; Thu, 12 Aug 2004 16:44:50 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7CKica21383; Thu, 12 Aug 2004 16:44:38 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9BD8F2B9D; Thu, 12 Aug 2004 16:43:36 -0400 (EDT) Message-ID: <411BD678.3020504@gnu.org> Date: Thu, 12 Aug 2004 20:44:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Eli Zaretskii Cc: jjohnstn@redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFA]: Fix for pending breakpoints in manually loaded/unloaded shlibs References: <41191D71.60204@redhat.com> <7494-Wed11Aug2004070352+0300-eliz@gnu.org> <411A4209.6020801@redhat.com> <411A5012.3000508@gnu.org> <9743-Wed11Aug2004205531+0300-eliz@gnu.org> <411A84B0.7020106@gnu.org> <2427-Thu12Aug2004064240+0300-eliz@gnu.org> <411B5E34.5020906@gnu.org> <3405-Thu12Aug2004214630+0300-eliz@gnu.org> In-Reply-To: <3405-Thu12Aug2004214630+0300-eliz@gnu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00474.txt.bz2 >>Date: Thu, 12 Aug 2004 08:10:28 -0400 >>> From: Andrew Cagney >> >>>> > >>>> > 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