[Bug gdb/30268] New: [gdb/dap] ERROR: timeout reading json header

[Bug gdb/30268] New: [gdb/dap] ERROR: timeout reading json header

[vries at gcc dot gnu.org]

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

            Bug ID: 30268
           Summary: [gdb/dap] ERROR: timeout reading json header
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Created attachment 14776
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14776&action=edit
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.

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

[Bug gdb/30268] [gdb/dap] ERROR: timeout reading json header

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
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.

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

[Bug gdb/30268] [gdb/dap] ERROR: timeout reading json header

[vries at gcc dot gnu.org]

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(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.

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

[Bug gdb/30268] [gdb/dap] ERROR: timeout reading json header

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.1
           Assignee|unassigned at sourceware dot org   |tromey at sourceware dot org
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Should be fixed now.
I meant to stick the bug reference into the commit, but forgot.

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