From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10160 invoked by alias); 26 Jun 2002 17:38:12 -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 10144 invoked from network); 26 Jun 2002 17:38:09 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 26 Jun 2002 17:38:09 -0000 Received: from 02-066.118.popsite.net ([66.19.120.66] helo=nevyn.them.org) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17NGji-0002r3-00; Wed, 26 Jun 2002 12:37:47 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17NGjh-0007ED-00; Wed, 26 Jun 2002 13:37:45 -0400 Date: Wed, 26 Jun 2002 10:38:00 -0000 From: Daniel Jacobowitz To: Glenn Chisholm Cc: gdb@sources.redhat.com Subject: Re: Threads GDB 5.2 Linux Help Needed Message-ID: <20020626173744.GA27720@nevyn.them.org> Mail-Followup-To: Glenn Chisholm , gdb@sources.redhat.com References: <5.1.0.14.2.20020626100642.02b055a0@ringer.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20020626100642.02b055a0@ringer.cisco.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-06/txt/msg00269.txt.bz2 On Wed, Jun 26, 2002 at 10:16:07AM -0700, Glenn Chisholm wrote: > G'Day, > I am currently working on a system that has gdb 5.2 when I debug a > threaded program it acts like I have no thread support. However if I take > the exact same gdb binary and the same program onto another host it works. > > Now I realize that I could be hitting 1000 different things > machine hopping however here it is on a working system: > > > ./gdb a.out > GNU gdb 5.2 > Copyright 2002 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: /local/gchishol/gdb/bin/a.out > [New Thread 1024 (LWP 15070)] > [New Thread 2049 (LWP 15079)] > [New Thread 1026 (LWP 15080)] > [New Thread 2051 (LWP 15081)] > > Program received signal SIGINT, Interrupt. > > Here it is on the non working system: > > # ./gdb a.out > GNU gdb 5.2 > Copyright 2002 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: /local/local1/core_dir/a.out > > Program received signal SIG32, Real-time event 32. > 0x2585ede6 in sigsuspend () from /lib/libc.so.6 > (gdb) > > For the life of me I can not work out what is happening. The libthread_db > seems to be available on both hosts. When I strace I can see the non > working system open the library on both hosts. In this case it is the > pthread.c from the gdb testsuite. The gdb is 5.2 built on the working > system, the other does not have a compiler. Am I missing a library? A clue? > > Can some one please point me at a starting point to get this working? Where > should I look what libraries should I check? What debug can I watch? Anyone > got a beer? Are you using the same library versions? I suspect you have a bad glibc version on one host. If you have ltrace available, see if the dlsym() calls in GDB fail (or use GDB on GDB to determine this). -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer