From: Jusctsch <schumjs@gmail.com>
To: gdb@sourceware.org
Subject: Thread exit error : gdb7.2 in FreeBSD (built from ports)
Date: Wed, 14 Sep 2011 14:27:00 -0000 [thread overview]
Message-ID: <32463912.post@talk.nabble.com> (raw)
Hello all,
I have been running into a particularly interesting issue.
When a thread exits in the application gdb is running, that exit doesn't
seem to propagate in some of the fields in gdb. In many cases, this will end
up crashing gdb (failing a thread_info=NULL gdbassert).
[Thread 803855580 (LWP 100241 Foo) exited]
error: Invalid selected thread.
thread.c:583: internal-error: set_running: Asser tion
`tp->state_ != THREAD_EXITED' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input
not from terminal]
thread.c:583: internal-error: set_running: Asser tion
`tp->state_ != THREAD_EXITED' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not
from terminal]
Is this a symptom of FreeBSD and some libraries? Or is this a gross gdb
issue?
--
View this message in context: http://old.nabble.com/Thread-exit-error-%3A-gdb7.2-in-FreeBSD-%28built-from-ports%29-tp32463912p32463912.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2011-09-14 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 14:27 Jusctsch [this message]
2011-09-14 14:41 ` Jusctsch
2011-09-14 15:04 ` Pedro Alves
2011-09-14 17:12 ` Jusctsch
2011-09-14 17:59 ` Pedro Alves
2011-09-22 15:49 ` Jusctsch
2011-09-22 16:34 ` Jusctsch
2011-09-22 17:11 ` Pedro Alves
[not found] ` <CAJoUm=HvAjAQVMVPEWs=deg0h6-m9+oMK3frD2_=bHRx+J1s5g@mail.gmail.com>
2011-09-23 19:31 ` John Schumacher
2011-09-22 22:30 John Schumacher
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=32463912.post@talk.nabble.com \
--to=schumjs@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).