From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-33117-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 28978 invoked by alias); 7 Oct 2008 14:02:51 -0000
Received: (qmail 28968 invoked by uid 22791); 7 Oct 2008 14:02:48 -0000
X-Spam-Check-By: sourceware.org
Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 07 Oct 2008 14:02:09 +0000
Received: from nan.false.org (localhost [127.0.0.1]) 	by nan.false.org (Postfix) with ESMTP id AC3CA1049C; 	Tue,  7 Oct 2008 14:02:06 +0000 (GMT)
Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) 	by nan.false.org (Postfix) with ESMTP id 81B0A1049A; 	Tue,  7 Oct 2008 14:02:06 +0000 (GMT)
Received: from drow by caradoc.them.org with local (Exim 4.69) 	(envelope-from <drow@caradoc.them.org>) 	id 1KnD8Y-0004XV-1y; Tue, 07 Oct 2008 10:02:06 -0400
Date: Tue, 07 Oct 2008 14:02:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Andr? P?nitz <apoenitz@trolltech.com>
Cc: gdb@sources.redhat.com
Subject: Re: How to use  auto-solib-add  properly?
Message-ID: <20081007140206.GA17209@caradoc.them.org>
Mail-Followup-To: Andr? P?nitz <apoenitz@trolltech.com>, 	gdb@sources.redhat.com
References: <200810071228.21179.apoenitz@trolltech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200810071228.21179.apoenitz@trolltech.com>
User-Agent: Mutt/1.5.17 (2008-05-11)
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-10/txt/msg00028.txt.bz2

On Tue, Oct 07, 2008 at 12:28:13PM +0200, Andr? P?nitz wrote:
> My idea was to use
> 
>   set auto-solib-add off
>   set stop-on-solib-events 1
> 
> and whenever a "shared library event" is encountered I'd do:
> 
>   for all shared objects except some big ones that I want to avoid do:
>      sharedlibrary <lib>
>   continue

Sonds like it might work.

> Is there a way to find out what exactly triggered the shared lib event?

Not in any existing version of GDB, though this is on my wishlist.

-- 
Daniel Jacobowitz
CodeSourcery