From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15155 invoked by alias); 9 Jul 2003 18:21:01 -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 15148 invoked from network); 9 Jul 2003 18:21:00 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 9 Jul 2003 18:21:00 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id OAA08207; Wed, 9 Jul 2003 14:12:15 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA09194; Wed, 9 Jul 2003 14:20:59 -0400 Message-ID: <099e01c34646$ea45e4d0$0202040a@catdog> From: "Kris Warkentin" To: "Daniel Jacobowitz" Cc: "Kevin Buettner" , "Andrew Cagney" , "Gdb@Sources.Redhat.Com" References: <062401c34590$97cd09b0$0202040a@catdog> <3F0B315E.7000702@redhat.com> <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> Subject: Re: [rfc] Print solib events in mi-mode Date: Wed, 09 Jul 2003 18:21:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-07/txt/msg00109.txt.bz2 > 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 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. ???? Kris