From: Marc Ferland <mferland@harfangmicro.com>
To: gdb@sourceware.org
Subject: Assert in linux_nat_resume
Date: Wed, 13 Aug 2008 01:02:00 -0000 [thread overview]
Message-ID: <48A1E2C4.7020007@harfangmicro.com> (raw)
Hi,
I've been having the following problem with GDB version 6.8 for a while now:
[New LWP 20436]
linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp !=
NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp !=
NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
I'm debugging a program with many threads and this happens often when I
close(pthread_exit()) and start threads (pthread_create). I really don't
know what is wrong.
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.
Regards,
Marc
next reply other threads:[~2008-08-12 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 1:02 Marc Ferland [this message]
2008-08-13 22:16 ` Daniel Jacobowitz
2008-08-14 9:10 ` Marc Ferland
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=48A1E2C4.7020007@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