From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15600 invoked by alias); 12 Aug 2004 12:58:04 -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 15591 invoked from network); 12 Aug 2004 12:58:03 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 12 Aug 2004 12:58:03 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1BvF9e-0002gV-0L; Thu, 12 Aug 2004 08:58:02 -0400 Date: Thu, 12 Aug 2004 12:58:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Eli Zaretskii , jjohnstn@redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFA]: Fix for pending breakpoints in manually loaded/unloaded shlibs Message-ID: <20040812125801.GB10224@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Eli Zaretskii , jjohnstn@redhat.com, gdb-patches@sources.redhat.com 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> <20040811204658.GA7231@nevyn.them.org> <411A9B5B.1080108@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <411A9B5B.1080108@gnu.org> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-08/txt/msg00454.txt.bz2 On Wed, Aug 11, 2004 at 06:19:07PM -0400, Andrew Cagney wrote: > >>I'm currently investigating gdb.threads/static.exp failures and to fix > >>>that I think I'll need to add a further observer event. > > > > > >Really? > > Really? > > > I think thread-db needs to try to initialize at two points: > >whenever a new shared library is loaded (converting the objfile hook to > >an observer would be nice, but independent) and whenever an inferior is > >created (conveniently we've got an observer for this already). > > Think PIE. I am, in fact, thinking about pie. Oh, you mean PIE... > For our purposes, both new executable loaded and new shlib loaded are > the same event - there's been an objfile_loaded event. There's no > reason to differentiate them. > > The new inferior event is orthogonal, and far more low level. I don't see how "new inferior" is any lower level than "new object". In any case, thread-db wants to initialize when these two conditions are true: (A) The inferior is running and (B) The thread library has been loaded So using an inferior created hook makes perfect sense to me... -- Daniel Jacobowitz