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

[Pedro Alves <pedro at codesourcery dot com>]

On Wednesday 14 September 2011 15:26:33, 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? 

It's a gdb bug.

We'd need more context to understand the problem.

You can debug gdb with gdb, and put a breakpoint on
`error' to catch that "error:", for example.  Where's
that coming from?  Sounds like your port has local
changes compared to the pristine FSF version?

> Or is this a gross gdb issue?

-- 
Pedro Alves