This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior
On Wed, Jan 18, 2006 at 02:44:30PM +0530, Girish Shilamkar wrote:
> > Definitely not. We need more information about this bug: what do you
> > do to reproduce it, since no one else has encountered it?
> >
> I have attached .c to reproduce this bug. I am using gdb-6.4 checked out
> from cvs, on Fedora Core 3, 32 bit Athlon processor. To reproduce the
> problem just run the application under gdb. No breakpoints, backtrace
> etc required. When the application exits this error can be seen.
As I suspected something is wrong with your host system, kernel,
environment, or similar. You may want to try a few others.
drow@caradoc:~% gdb ./mult
GNU gdb 6.4-debian
Copyright 2005 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 "x86_64-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".
(gdb) r
Starting program: /home/drow/mult
[Thread debugging using libthread_db enabled]
[New Thread 46912500755888 (LWP 15465)]
[New Thread 1082132832 (LWP 15471)]
[New Thread 1090525536 (LWP 15472)]
[New Thread 1098918240 (LWP 15473)]
[New Thread 1107310944 (LWP 15474)]
[New Thread 1115703648 (LWP 15475)]
[Thread 1082132832 (LWP 15471) exited]
[Thread 1090525536 (LWP 15472) exited]
[Thread 1098918240 (LWP 15473) exited]
[Thread 1107310944 (LWP 15474) exited]
[Thread 1115703648 (LWP 15475) exited]
Program exited normally.
(gdb)
Verified on both 32-bit and 64-bit hosts.
--
Daniel Jacobowitz
CodeSourcery