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/30644] New: [gdb/dap] ERROR: tcl error sourcing gdb.dap/stop-at-main.exp
Date: Mon, 17 Jul 2023 08:22:32 +0000	[thread overview]
Message-ID: <bug-30644-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30644
           Summary: [gdb/dap] ERROR: tcl error sourcing
                    gdb.dap/stop-at-main.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: ---

Created attachment 14974
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14974&action=edit
gdb.log

As noted here (
https://sourceware.org/pipermail/gdb-patches/2023-July/200945.html ), commit
75ec0982978 ("Use correct inferior in Inferior.read_memory et al") breaks
test-case gdb.dap/stop-at-main.exp:
...
{"request_seq": 2, "type": "response", "command": "launch", "success": true,
"seq": 3}PASS: gdb.dap/stop-at-main.exp: startup - launch success
>>> {"seq": 3, "type": "request", "command": "configurationDone"}
Content-Length: 97^M
^M
{"request_seq": 3, "type": "response", "command": "configurationDone",
"success": true, "seq": 4}PASS: gdb.dap/stop-at-main.exp: start inferior
success
ERROR: eof reading json header
    while executing
"error "eof reading json header""
    invoked from within
"expect {
-i exp19 -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/stop-at-main.exp.
...

Unfortunately, the failure comes in the form of an ERROR.

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

             reply	other threads:[~2023-07-17  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  8:22 vries at gcc dot gnu.org [this message]
2023-07-17  8:23 ` [Bug dap/30644] " vries at gcc dot gnu.org
2023-07-17  8:24 ` vries at gcc dot gnu.org
2023-07-17  8:25 ` vries at gcc dot gnu.org
2023-07-17 13:21 ` tromey at sourceware dot org
2023-07-17 17:38 ` tromey at sourceware dot org
2023-07-19 13:12 ` cvs-commit at gcc dot gnu.org
2023-07-19 13:43 ` pedro at palves dot net
2023-07-19 14:10 ` vries at gcc dot gnu.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-30644-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).