This is the mail archive of the
mailing list for the GDB project.
Re: gdb continues when I want "next"
- From: Markus dot Grunwald at pruftechnik dot com
- To: gdb at sourceware dot org
- Date: Wed, 7 Mar 2007 12:20:15 +0100
- Subject: Re: gdb continues when I want "next"
> > 2) Conditions as above, but: Sometimes, I get this when reaching the
> > breakpoint for the first time:
> > Breakpoint 1, CPTLinearGraphic::CalculateLinLines (this=0x9251de0)
> > at
> > /home/gru/projects/vxp/branches/branch-0-2-10-
> > (gdb) n
> > (gdb) n
> > Detaching after fork from child process 29873.
> > [Thread -1863816272 (LWP 29869) exited]
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > [Switching to Thread -1863816272 (LWP 29869)]
> > 0xb7446891 in __nptl_death_event () from
> > /lib/tls/i686/cmov/libpthread.so.0
> I have no idea. Part of this sounds like GDB is confused by an
> excessive rate of forking and thread creation / destruction.
We are using threads, of course. But I doubt there is an "excessive" rate
of forking/threading ...
> I don't think we will be able to help you without a testcase we can
> use to reproduce your problems.
Hmm, that's bad. I can't give that code away, besides its size is 340MB
... Isn't there anything that I could do myself when you give me some
instructions, patches, whatever ?
(Sorry for sending this twice - I just hate lotus notes.)