public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30686] New: [gdb/dap] ERROR: eof reading json header in gdb.dap/cond-bp.exp
Date: Wed, 26 Jul 2023 14:16:57 +0000	[thread overview]
Message-ID: <bug-30686-4717@http.sourceware.org/bugzilla/> (raw)

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

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

Gdb build with -O0 at commit bcf43b33cfd ("[gdb/testsuite] Drop -nostdlib in
gdb.dwarf2/typeddwarf.exp").

Stress test of gdb.dap/*.exp:
...
$ for n in $(seq 1 25); do ./test.sh ; cat
leap-15-4/build/gdb/testsuite/gdb.{sum,log} ; done 2>&1 | tee LOG | grep "# of
expected "
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            214
# of expected passes            214
# of expected passes            214
# of expected passes            214
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
# of expected passes            224
...

The 214 is due to:
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp ...
PASS: gdb.dap/cond-bp.exp: startup - initialize success
PASS: gdb.dap/cond-bp.exp: startup - launch success
PASS: gdb.dap/cond-bp.exp: set invalid breakpoints success
PASS: gdb.dap/cond-bp.exp: breakpoint 1 invalid
PASS: gdb.dap/cond-bp.exp: breakpoint 1 has message
PASS: gdb.dap/cond-bp.exp: breakpoint 2 invalid
PASS: gdb.dap/cond-bp.exp: breakpoint 2 has message
ERROR: eof reading json header
    while executing
"error "eof reading json header""
    invoked from within
"expect {
-i exp9 -timeout 10
        -re "^Content-Length: (\[0-9\]+)\r\n" {
            set length $expect_out(1,string)
            exp_continue
        }
        -re "^(\[^\r\n\]+)\..."
    ("uplevel" body line 1)
    invoked from within
"uplevel $body" NONE eof reading json header
ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp.
ERROR: eof reading json header
    while executing
"error "eof reading json header""
    ("uplevel" body line 2)
    invoked from within
"uplevel $error_sect"
    invoked from within
"remote_expect host 10 {
        -re "^Content-Length: (\[0-9\]+)\r\n" {
            set length $expect_out(1,string)
            exp_continue
        }
        -re "^(\[^\r\n\]+)\r\n" {..."
    ("uplevel" body line 1)
    invoked from within
"uplevel remote_expect host $tmt $expcode"
    invoked from within
"gdb_expect {
        -re "^Content-Length: (\[0-9\]+)\r\n" {
            set length $expect_out(1,string)
            exp_continue
        }
        -re "^(\[^\r\n\]+)\r\n" {
            # Any..."
    (procedure "_dap_read_json" line 3)
    invoked from within
"_dap_read_json"
    (procedure "_dap_read_response" line 4)
    invoked from within
"_dap_read_response $command $seq"
    (procedure "dap_request_and_response" line 3)
    invoked from within
"dap_request_and_response $command $obj"
    (procedure "dap_check_request_and_response" line 2)
    invoked from within
"dap_check_request_and_response "set conditional breakpoint" \
             setBreakpoints \
             [format {o source [o path [%s]] \
                          breakpoints [a [o li..."
    (file "/data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp" line 52)
    invoked from within
"source /data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source /data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
...

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

             reply	other threads:[~2023-07-26 14:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 14:16 vries at gcc dot gnu.org [this message]
2023-07-26 14:18 ` [Bug dap/30686] " vries at gcc dot gnu.org
2023-07-26 14:44 ` vries at gcc dot gnu.org
2023-07-26 15:02 ` vries at gcc dot gnu.org
2023-07-26 17:38 ` tromey at sourceware dot org
2023-07-26 20:29 ` tromey at sourceware dot org
2023-07-27 13:41 ` tromey at sourceware dot org
2023-07-27 13:59 ` tromey at sourceware dot org
2023-07-27 13:59 ` tromey at sourceware dot org
2023-07-28 12:18 ` cvs-commit at gcc dot gnu.org
2023-07-28 12:19 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30686-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).