Re: Thread exit error : gdb7.2 in FreeBSD (built from ports)

[Jusctsch <schumjs@gmail.com>]

I noticed this 'bad' behavior only in standard console gdb. The asserts do
not happen in gdb-mi mode.


Jusctsch wrote:
> 
> 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-tp32463912p32464063.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.