This is the mail archive of the
mailing list for the GDB project.
Re: gdb bugs showing while working on libcwd
- From: Daniel Jacobowitz <dmj+ at andrew dot cmu dot edu>
- To: Carlo Wood <carlo at alinoe dot com>
- Cc: Liam Stewart <liams at redhat dot com>, gdb at sources dot redhat dot com
- Date: Thu, 23 May 2002 20:57:58 -0500
- Subject: Re: gdb bugs showing while working on libcwd
- References: <20020522115242.C28512@redhat.com> <20020523153816.A4454@alinoe.com> <20020523094527.B25730@redhat.com> <20020524023546.A19030@alinoe.com>
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