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 testsuite/26947] New: gdb.tui/new-layout.exp and tcl 8.5 Date: Wed, 25 Nov 2020 23:40:57 +0000 [thread overview] Message-ID: <bug-26947-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26947 Bug ID: 26947 Summary: gdb.tui/new-layout.exp and tcl 8.5 Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- In test-case gdb.tui/new-layout.exp we find a test: ... gdb_test "tui new-layout example src 1}" \ "Extra '\}' in layout specification" ... before commit 4d91ddd342b "[gdb/testsuite] Fix unbalanced braces in gdb.tui/new-layout.exp", and after that commit: ... gdb_test "tui new-layout example src 1\}" \ "Extra '\}' in layout specification" ... The commit was supposed to solve this on SLE-11 with tcl 8.5: ... (gdb) UNRESOLVED: gdb.tui/new-layout.exp: testcase aborted due to invalid command name: } ERROR: Couldn't send tui new-layout example src 1} to GDB. UNRESOLVED: gdb.tui/new-layout.exp: tui new-layout example src 1} ... but after the commit, we have the identical: ... (gdb) UNRESOLVED: gdb.tui/new-layout.exp: testcase aborted due to invalid command name: } ERROR: Couldn't send tui new-layout example src 1} to GDB. UNRESOLVED: gdb.tui/new-layout.exp: tui new-layout example src 1} ... After adding another escape, such that we have: ... gdb_test "tui new-layout example src 1\\}" \ "Extra '\}' in layout specification" ... we get rid of the ERROR/UNRESOLVED, but now have a FAIL: ... (gdb) tui new-layout example src 1\}^M Trailing junk at: \}^M (gdb) FAIL: gdb.tui/new-layout.exp: tui new-layout example src 1\} ... There's no amount of escapes that makes this go as with tcl 8.6, where we simply have: ... (gdb) tui new-layout example src 1}^M Extra '}' in layout specification^M (gdb) PASS: gdb.tui/new-layout.exp: tui new-layout example src 1} ... Using the two-backslash escape variant with tcl 8.6, we get the identical FAIL: ... (gdb) tui new-layout example src 1\}^M Trailing junk at: \}^M (gdb) FAIL: gdb.tui/new-layout.exp: tui new-layout example src 1\} ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-11-25 23:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-25 23:40 vries at gcc dot gnu.org [this message] 2020-11-26 0:39 ` [Bug testsuite/26947] " vries at gcc dot gnu.org 2020-12-10 16:56 ` vries at gcc dot gnu.org 2020-12-10 22:44 ` cvs-commit at gcc dot gnu.org 2020-12-10 22:45 ` 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-26947-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: linkBe 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).