From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32642 invoked by alias); 10 Nov 2003 21:39:13 -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 32631 invoked from network); 10 Nov 2003 21:39:11 -0000 Received: from unknown (HELO smtp3.andrew.cmu.edu) (128.2.10.83) by sources.redhat.com with SMTP; 10 Nov 2003 21:39:11 -0000 Received: from UNIX45.andrew.cmu.edu (UNIX45.andrew.cmu.edu [128.2.13.175]) by smtp3.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id hAALdCQo004299; Mon, 10 Nov 2003 16:39:12 -0500 Date: Mon, 10 Nov 2003 21:39:00 -0000 From: jdavin@cmu.edu X-X-Sender: jdavin@unix45.andrew.cmu.edu To: Andrew Cagney cc: gdb@sources.redhat.com Subject: Re: gdb not working with older glibc In-Reply-To: <3FAFFC98.1040706@redhat.com> Message-ID: References: <3FAFFC98.1040706@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-11/txt/msg00083.txt.bz2 Well that pretty much was the exact output. Here's the version info too: GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) run Starting program: /path/(name-omitted) Program received signal SIG32, Real-time event 32. 0x0811c7f6 in __sigsuspend (set=0xbffff380) at ../sysdeps/unix/sysv/linux/sigsuspend.c:45 45 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory. in ../sysdeps/unix/sysv/linux/sigsuspend.c Current language: auto; currently c And for gdb 6.0 working, it's just the same thing without the error/crash. -John On Mon, 10 Nov 2003, Andrew Cagney wrote: > What is the exact output of GDB 6.0 (working and non-working)? > > The problem is most likely that GDB is loading the lated libthread_db > and that library is refusing to debug the older glibc. > > Perhaphs there should be a "set libthread_db ... command?" > > Andrew > > >