From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17182 invoked by alias); 24 May 2002 01:58:05 -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 17162 invoked from network); 24 May 2002 01:58:03 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 24 May 2002 01:58:03 -0000 Received: from drow by crack.them.org with local (Exim 3.12 #1 (Debian)) id 17B4L8-0005c2-00; Thu, 23 May 2002 20:57:58 -0500 Date: Thu, 23 May 2002 18:58:00 -0000 From: Daniel Jacobowitz To: Carlo Wood Cc: Liam Stewart , gdb@sources.redhat.com Subject: Re: gdb bugs showing while working on libcwd Message-ID: <20020523205758.A21537@crack.them.org> References: <20020522115242.C28512@redhat.com> <20020523153816.A4454@alinoe.com> <20020523094527.B25730@redhat.com> <20020524023546.A19030@alinoe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020524023546.A19030@alinoe.com>; from carlo@alinoe.com on Fri, May 24, 2002 at 02:35:46AM +0200 X-SW-Source: 2002-05/txt/msg00267.txt.bz2 On Fri, May 24, 2002 at 02:35:46AM +0200, Carlo Wood wrote: > You now should have a core file. Here is what I next do > what reveals a problem with gdb: > > ~/c++/libcwd/testsuite>gdb threads_threads_shared core.21920 > GNU gdb Red Hat Linux (5.1-1) > Copyright 2001 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 "i386-redhat-linux"... > > warning: core file may not match specified executable file. > Core was generated by `threads_threads_shared'. > Program terminated with signal 6, Aborted. > Reading symbols from /home/carlo/c++/libcwd/.libs/libcwd_r.so.0...done. > Loaded symbols for /home/carlo/c++/libcwd/.libs/libcwd_r.so.0 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /usr/local/gcc-3.0.4/lib/libstdc++.so.3...done. > Loaded symbols for /usr/local/gcc-3.0.4/lib/libstdc++.so.3 > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from /usr/local/gcc-3.0.4/lib/libgcc_s.so.1...done. > Loaded symbols for /usr/local/gcc-3.0.4/lib/libgcc_s.so.1 > Reading symbols from /lib/libpthread.so.0...done. > > warning: Unable to set global thread event mask: generic error > [New Thread 1024 (LWP 21868)] This specific bug is, however, fixed in GDB 5.2. It won't help much. You are trying to debug a multithreaded application via core dump; only via my or Mark Gross at Intel's patches does Linux dump enough information to core files in order to see threads there. You can find them in the archives of the linux-kernel list. -- Daniel Jacobowitz Debian GNU/Linux Developer MontaVista Software Carnegie Mellon University