From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5869 invoked by alias); 12 Jan 2004 23:12:39 -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 5852 invoked from network); 12 Jan 2004 23:12:38 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 12 Jan 2004 23:12:38 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AgBEa-0007N8-Ts; Mon, 12 Jan 2004 18:12:36 -0500 Date: Mon, 12 Jan 2004 23:12:00 -0000 From: Daniel Jacobowitz To: Richard Henderson Cc: gdb@gcc.gnu.org Subject: Re: turn off thread support? Message-ID: <20040112231236.GA27775@nevyn.them.org> Mail-Followup-To: Richard Henderson , gdb@gcc.gnu.org References: <20040112230631.GA32178@twiddle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040112230631.GA32178@twiddle.net> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg00154.txt.bz2 On Mon, Jan 12, 2004 at 03:06:31PM -0800, Richard Henderson wrote: > Is there a way to temporarily turn off thread support in gdb? > Also, is there a way to load an alternate thread_db library? > > I'm trying to debug libpthread itself, and keep getting told > that the process no longer exists after hitting the SEGV. Right now, neither easily. But if you LD_PRELOAD a different libthread_db.so.1, then dlopen will use the one you gave it; and I imagine that if you LD_PRELOAD a dummy library with that soname, then the failed dlsym() calls will cause GDB to disable thread handling. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer