[Bug gdb/23417] using "set non-stop on" and "set follow-exec-mode new" together causes GDB to crash

["gdb-bug-report at mailinator dot com" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #4 from gdb-bug-report at mailinator dot com ---
Created attachment 11133
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11133&action=edit
The created core

adding a catch point on the newer build results in the same crash from before.

********************************************************************************

vagrant@vagrant-ubuntu-trusty-64:~$ gdb -iex "set non-stop on" -iex "set
follow-exec-mode new" -ex "catch exec" -ex r --args /bin/bash -c ls
GNU gdb (GDB) 8.1.90.20180716-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/bash...(no debugging symbols found)...done.
Catchpoint 1 (exec)
Starting program: /bin/bash -c ls
process 30216 is executing new program: /bin/ls
[New inferior 2 (process 0)]
[New process 30216]

[1]+  Stopped                 gdb -iex "set non-stop on" -iex "set
follow-exec-mode new" -ex "catch exec" -ex r --args /bin/bash -c ls
vagrant@vagrant-ubuntu-trusty-64:~$ fg
gdb -iex "set non-stop on" -iex "set follow-exec-mode new" -ex "catch exec" -ex
r --args /bin/bash -c ls
../../gdb-source/gdb/thread.c:93: internal-error: thread_info*
inferior_thread(): Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

../../gdb-source/gdb/thread.c:93: internal-error: thread_info*
inferior_thread(): Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted (core dumped)

********************************************************************************

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