[Bug dap/30680] [gdb/dap] ThreadSanitizer: data race gdbsupport/event-pipe.h:44 in event_pipe::is_open() const

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

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

--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #10)
> I definitely (but intermittently) see the failure with the assert patch
> applied.
> I'm not much closer to finding the problem, though.
> I think the challenge is finding out what bit of code might be
> unblocking SIGCHLD on this thread.

I set a breakpoint on pthread_create, and ran a basic dap test.  For the dap
threads, there's a backtrace:
...
#24 0x00007ffff7401b7e in _PyObject_FastCallDict (func=<function at remote
0x7fffec10c1e0>, args=0x0, 
    nargs=<optimized out>, kwargs=0x0) at Objects/abstract.c:2310
#25 0x0000000000a353ea in dap_interp::init (this=0x2bfdac0, top_level=true)
    at /data/vries/gdb/src/gdb/python/py-dap.c:82
#26 0x000000000089ef02 in interp_set (interp=0x2bfdac0, top_level=true) at
/data/vries/gdb/src/gdb/interps.c:140
#27 0x000000000089f197 in set_top_level_interpreter (name=0x286de50
<interpreter_p[abi:cxx11]+16> "dap")
    at /data/vries/gdb/src/gdb/interps.c:209
#28 0x000000000091ac77 in captured_main_1 (context=0x7fffffffdaa0) at
/data/vries/gdb/src/gdb/main.c:1139
...
so I tried to wrap the code around the py-dap.c:82:
...
  gdbpy_ref<> result_obj (PyObject_CallObject (func.get (), nullptr));
  if (result_obj == nullptr)
    gdbpy_handle_exception ();
...
in the gdb::block_signals wrapper, but that didn't fix it either.

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