From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7298 invoked by alias); 12 Feb 2009 20:17:52 -0000 Received: (qmail 7290 invoked by uid 22791); 12 Feb 2009 20:17:51 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_13 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 12 Feb 2009 20:17:46 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 14DAE107F8; Thu, 12 Feb 2009 20:17:45 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id ACDE9107F2; Thu, 12 Feb 2009 20:17:44 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LXi0G-0008UV-8V; Thu, 12 Feb 2009 15:17:44 -0500 Date: Thu, 12 Feb 2009 20:26:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: Tom Tromey , Marc Khouzam , gdb-patches@sources.redhat.com, Nick Roberts Subject: Re: MI solib notification Message-ID: <20090212201744.GA32437@caradoc.them.org> Mail-Followup-To: Vladimir Prus , Tom Tromey , Marc Khouzam , gdb-patches@sources.redhat.com, Nick Roberts References: <200901310010.46738.vladimir@codesourcery.com> <20090212180215.GA22097@caradoc.them.org> <200902122311.05275.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902122311.05275.vladimir@codesourcery.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00295.txt.bz2 On Thu, Feb 12, 2009 at 11:11:04PM +0300, Vladimir Prus wrote: > Can you write down the comment that disable_breakpoints_in_unloaded_shlib > would have to contain to explain all this? ;-) I assume it will go like this: > > Don't emit any message here for a.out, because for all the other > targets some other code calls some other function that arranges for > this message to not be printed when rerunning the program... > > In other words, the problem with checking for a.out is that it deeply depends on > intricate details of some other code. It's not about the message, but about the disabling. I mean: /* SunOS a.out shared libraries are always mapped, so do not disable breakpoints; they will only be reported as unloaded through clear_solib when GDB discards its shared library list. See clear_solib for more information. */ -- Daniel Jacobowitz CodeSourcery