From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20941 invoked by alias); 9 Jul 2003 18:30:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20934 invoked from network); 9 Jul 2003 18:30:44 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 9 Jul 2003 18:30:44 -0000 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19aJiD-0006OD-00; Wed, 09 Jul 2003 14:30:41 -0400 Date: Wed, 09 Jul 2003 18:30:00 -0000 From: Daniel Jacobowitz To: Kris Warkentin Cc: Kevin Buettner , Andrew Cagney , "Gdb@Sources.Redhat.Com" Subject: Re: [rfc] Print solib events in mi-mode Message-ID: <20030709183041.GA24498@nevyn.them.org> Mail-Followup-To: Kris Warkentin , Kevin Buettner , Andrew Cagney , "Gdb@Sources.Redhat.Com" References: <064e01c34615$0b152ae0$0202040a@catdog> <20030709150847.GA19020@nevyn.them.org> <087801c34630$479de310$0202040a@catdog> <20030709162430.GA20778@nevyn.them.org> <090201c3463f$acc520f0$0202040a@catdog> <1030709174134.ZM2191@localhost.localdomain> <093901c34642$884d0280$0202040a@catdog> <095501c34644$31dec7b0$0202040a@catdog> <20030709180553.GA23828@nevyn.them.org> <099e01c34646$ea45e4d0$0202040a@catdog> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <099e01c34646$ea45e4d0$0202040a@catdog> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-07/txt/msg00110.txt.bz2 On Wed, Jul 09, 2003 at 02:21:28PM -0400, Kris Warkentin wrote: > > On Wed, Jul 09, 2003 at 02:02:00PM -0400, Kris Warkentin wrote: > > > Someone just pointed something out to me. "set stop-on-solib-events 1" > is > > > NOT enable-load-catchpoint or anything else. Yes, those things should > exist > > > for all solib platforms but the bottom line is that stop-on-solib-events > is > > > not currently mi-enabled and it should be. > > > > > > I want to make that command result in proper mi output, regardless of > any > > > other things which might be implemented in the future. > > > > And I want load catchpoints fixed, so that stop-on-solib-events is > > NEVER MI-enabled, so that it can be removed instead of supported for > > years. It is in every way inferior to catchpoints. That was my point. > > Well I want an ice cream bar so I'm going to go get one. :-P Curse you, now I want ice cream. > Alright then. I see that SOM and PA64 both implement > SOLIB_CREATE_CATCH_*LOAD_HOOK and most everyone else just errors out if you > try. Should we be adding these functions to the target_so_ops vector? Does > every target that supports solibs build solib.c? If so, we could tweak the > defines to use the vector and have a default implementation that prints an > error. That way solib-svr4 and friends can implement these functions in the > backend. > > ???? That's not really the problem - the breakpoint is already there, it's the same breakpoint we stop at for stop-on-solib-events. The real trick is going to be reporting the events - SOLIB_HAVE_LOAD_EVENT and SOLIB_LOADED_LIBRARY_PATHNAME. The model has to change a little since more than one library can be reported at once in the svr4 model. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer