[Bug gdb/26761] thread.c:95: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed

["simark at simark dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=26761

--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Parke from comment #6)
> I encounter a similar bug.  Easy to reproduce.
> 
> On Arch Linux:
> 
> $  gdb  --version
> GNU gdb (GDB) 10.2
> [snip]
> 
> $  gdb  -q -ex run /bin/true
> Reading symbols from /bin/true...
> (No debugging symbols found in /bin/true)
> Starting program: /usr/bin/true 
> [Inferior 1 (process 339) exited normally]
> ../../gdb/thread.c:95: internal-error: thread_info* inferior_thread():
> Assertion `current_thread_ != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> 
> This is a bug, please report it.  For instructions, see:
> <https://www.gnu.org/software/gdb/bugs/>.
> 
> Aborted (core dumped)
> 
> $  cat  ~/.gdbinit
> define  hook-quit
>   set  confirm  off
> end
> 
> python
> 
> def  exit_handler  ( event ):
>   if  hasattr ( event, 'exit_code' )  and  event .exit_code == 0:
>     gdb .execute ( "quit" )
> 
> gdb .events .exited .connect ( exit_handler )
> 
> end
> 
> ----
> 
> I encounter a similar bug on Ubuntu 20.04.
> 
> $  gdb --version
> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
> [snip]
> 
> $  gdb  -q  -ex run /bin/true
> Reading symbols from /bin/true...
> (No debugging symbols found in /bin/true)
> Starting program: /usr/bin/true 
> [Inferior 1 (process 4134946) exited normally]
> /build/gdb-OxeNvS/gdb-9.2/gdb/inferior.c:283: internal-error: inferior*
> find_inferior_pid(int): Assertion `pid != 0' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> 
> This is a bug, please report it.  For instructions, see:
> <http://www.gnu.org/software/gdb/bugs/>.
> 
> Aborted (core dumped)
> 
> Possibly related:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27682

Although the symptom is the same, the root cause for this particular assertion
to fail can be one of many things.  So I would suggest filing a new bug, with a
title that is specific to what you are doing (e.g. "Assertion failure when
using Python exit event handler".

-- 
You are receiving this mail because:
You are on the CC list for the bug.