From: Markus.Grunwald@pruftechnik.com
To: gdb@sourceware.org
Subject: Re: gdb continues when I want "next"
Date: Wed, 07 Mar 2007 11:20:00 -0000 [thread overview]
Message-ID: <OF78548181.10514C4A-ONC1257297.003E319B-C1257297.003E4F87@pruftechnik.com> (raw)
Hello,
> > 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-
> X/Dafit_Code/drawdevices/CPTLinearGraphic.cpp:1640
> > (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.)
Best regards
Markus Grunwald
Softwaredevelopment
next reply other threads:[~2007-03-07 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 11:20 Markus.Grunwald [this message]
2007-03-07 12:13 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-03-02 13:44 Markus.Grunwald
2007-03-02 13:57 ` Daniel Jacobowitz
2007-03-07 19:09 ` Michael Snyder
2007-03-08 14:50 ` Markus.Grunwald
2007-03-08 15:01 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF78548181.10514C4A-ONC1257297.003E319B-C1257297.003E4F87@pruftechnik.com \
--to=markus.grunwald@pruftechnik.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox