[Bug remote/26614] AddressSanitizer: heap-use-after-free of extended_remote_target in remote_async_inferior_event_handler

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
I did another series with the same circumstances, but with gdb setup to
generate a backtrace after running:
...
diff --git a/gdb/testsuite/gdb.multi/multi-target.exp.tcl
b/gdb/testsuite/gdb.multi
/multi-target.exp.tcl
index 8dcd413f58..e2c78214c4 100644
--- a/gdb/testsuite/gdb.multi/multi-target.exp.tcl
+++ b/gdb/testsuite/gdb.multi/multi-target.exp.tcl
@@ -106,11 +106,13 @@ proc cleanup_gdbservers { } {

 proc setup {non-stop} {
     global gcorefile gcore_created
-    global binfile
+    global binfile GDB

     cleanup_gdbservers
-    clean_restart ${binfile}
-
+    save_vars GDB {
+       set GDB "/usr/bin/gdb -iex \"set trace-commands on\" -batch -ex run -ex
backtrace -ex quit --args $GDB"
+       clean_restart ${binfile}
+    }
     # multi-target depends on target running in non-stop mode.  Force
     # it on for remote targets, until this is the default.
     gdb_test_no_output "maint set target-non-stop on"
...

At run 28, I ran into:
...
(gdb) PASS: gdb.multi/multi-target-continue.exp: continue: non-stop=on:
inferior 2
Remote debugging from host ::1, port 42094^M
Process
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.multi/multi-target-continue/multi-target-continue
created; pid = 25075^M
monitor exit^M
(gdb) Killing process(es): 25075^M
^M
Thread 1 "gdb" received signal SIGSEGV, Segmentation fault.^M
0x00000000004aa8fd in mark_async_event_handler (async_handler_ptr=0x0) at
/home/vries/gdb_versions/devel/src/gdb/async-event.c:269^M
269       async_handler_ptr->ready = 1;^M
+backtrace^M
#0  0x00000000004aa8fd in mark_async_event_handler (async_handler_ptr=0x0) at
/home/vries/gdb_versions/devel/src/gdb/async-event.c:269^M
#1  0x00000000008da4c9 in remote_async_inferior_event_handler (data=0x1f59990)
at /home/vries/gdb_versions/devel/src/gdb/remote.c:14179^M
#2  0x00000000004aa95e in check_async_event_handlers () at
/home/vries/gdb_versions/devel/src/gdb/async-event.c:295^M
#3  0x0000000000d0ead1 in gdb_do_one_event () at
/home/vries/gdb_versions/devel/src/gdbsupport/event-loop.cc:194^M
#4  0x0000000000795ec7 in start_event_loop () at
/home/vries/gdb_versions/devel/src/gdb/main.c:356^M
#5  0x0000000000795fe7 in captured_command_loop () at
/home/vries/gdb_versions/devel/src/gdb/main.c:416^M
#6  0x0000000000797662 in captured_main (data=0x7fffffffd310) at
/home/vries/gdb_versions/devel/src/gdb/main.c:1253^M
...

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