Created attachment 14776 [details] gdb.log I applied a recently proposed patch "Fix race in DAP startup" to see if that would fix the instability in the dap tests I see, but I still run into problems.
This trace looks a lot like the race, and: {"type": "event", "event": "output", "body": {"category": "stdout", "output": " File \"/data/vries/gdb/leap-15-4/build/gdb/data-directory/python/gdb/dap/server.py\", line 115, in main_loop\n"}, "seq": 7} the line number here seems wrong, like it's from the version without the race patch. Did you maybe not "make" after applying? The test suite picks up the Python code from data-directory so a build is needed before running the tests.
(In reply to Tom Tromey from comment #1) > This trace looks a lot like the race, and: > > {"type": "event", "event": "output", "body": {"category": "stdout", > "output": " File > \"/data/vries/gdb/leap-15-4/build/gdb/data-directory/python/gdb/dap/server. > py\", line 115, in main_loop\n"}, "seq": 7} > > the line number here seems wrong, like it's from the version without > the race patch. Did you maybe not "make" after applying? The > test suite picks up the Python code from data-directory so a build > is needed before running the tests. /me facepalms. Yes, that's what happened, sorry for the confusion. After rebuilding, the tests pass reliably. So we can close this PR once the patch is committed.
Should be fixed now. I meant to stick the bug reference into the commit, but forgot.