[Bug gdb/29278] gdb crashes on interrupt (non-stop mode, target extended-remote)

["Manfred.Steiner at gmx dot at" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #3 from Manfred Steiner <Manfred.Steiner at gmx dot at> ---
There are some more similar problems:

1) start gdb (for target avr)
2) (gdb) set non-stop 1
3) (gdb) file ...
4) (gdb) target extended-remote ...

The stub returns no thread running (in my point of view OK for extended-remote
mode); means "$qfThreadInfo#bb" -> "$l#6c" in gdb protocol.

5) (gdb) load

gdb crashes
  ...
  .../binutils-gdb/gdb/thread.c:85
  ...
  .../binutils-gdb/gdb/symfile.c:1836 
  ...

because command load (symfile.c:1836) is not checking if inferior has threads.
In this case inferior has no threads, so current_thread is nullptr, and
function inferior_thread (thread.c:85) fails on gdb_assert (current_thread_ !=
nullptr);

Simple fix possible with additional check in load command:

add on binutils-gdb/gdb/symfile.c:1836: 
if (current_inferior()->ptid_thread_map.size() == 0) {
  error (_("Error: current inferior has no threads, cannot load"));
  return;
}

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