From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12123 invoked by alias); 9 Jul 2003 19:12:38 -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 12106 invoked from network); 9 Jul 2003 19:12:37 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 9 Jul 2003 19:12:37 -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 PAA10506; Wed, 9 Jul 2003 15:03:52 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id PAA27388; Wed, 9 Jul 2003 15:12:36 -0400 Message-ID: <09d201c3464e$2011b290$0202040a@catdog> From: "Kris Warkentin" To: "Daniel Jacobowitz" Cc: "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> <20030709183041.GA24498@nevyn.them.org> Subject: Re: [rfc] Print solib events in mi-mode Date: Wed, 09 Jul 2003 19:12: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/msg00111.txt.bz2 > 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. Well, SOLIB_LOADED_LIBRARY_PATHNAME is only used twice. Once it just fills a string (triggered_dll_pathname) which is only used for printing. Therefore we could return a comma separated list or something pretty like that. The other is just to compare against a dll_pathname so we could get away with creating a SOLIB_WAS_(UN)LOADED(pid, "libname") and have the backend check through the list for libname. Okay...that seems reasonable. Another question: since we've already got a solib breakpoint set in svr4, we don't need to call create_solib_load_event_breakpoint() like somsolib.c and pa64solib.c do. Can you have multiple types associated with a single break or do we just set another at the same address? cheers, Kris