From: Marc Ferland <mferland@harfangmicro.com>
To: Marc Ferland <mferland@harfangmicro.com>, gdb@sourceware.org
Subject: Re: Assert in linux_nat_resume
Date: Thu, 14 Aug 2008 09:10:00 -0000 [thread overview]
Message-ID: <48A1FBE3.5090702@harfangmicro.com> (raw)
In-Reply-To: <20080812192948.GA23036@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Tue, Aug 12, 2008 at 03:21:40PM -0400, Marc Ferland wrote:
>> I'm pretty sure it has something to do with my program but I don't know
>> where to start (Debugging with printf() is a rather tedious task!). Any
>> help would be greatly appreciated.
>
> The first thing to try is definitely a snapshot of current CVS GDB.
>
I tried with 6.8.50.20080812-cvs seems to have a similar problem.
[New LWP 29169]
linux-nat.c:1669: internal-error: linux_nat_resume: Assertion `lp !=
NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
After further testing, this seems to happen only when I have a
breakpoint somewhere inside a thread. The first time I hit the
breakpoint everything is fine. But if I exit a thread and recreate it, I
get the previously mentioned message.
I also found a workaround:
- The first time I hit the breakpoint, I delete it;
- I place a breakpoint on the pthread_join() call for this thread;
- When I break on the pthread_join() call, I recreate the breakpoint
inside the thread;
This way, I'm able to break inside the thread every time I create it
(pthread_create()).
Marc
prev parent reply other threads:[~2008-08-12 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 1:02 Marc Ferland
2008-08-13 22:16 ` Daniel Jacobowitz
2008-08-14 9:10 ` Marc Ferland [this message]
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=48A1FBE3.5090702@harfangmicro.com \
--to=mferland@harfangmicro.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