public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/30458] FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap Date: Wed, 21 Jun 2023 14:16:52 +0000 [thread overview] Message-ID: <bug-30458-4717-o3WsLCfRnW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30458-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30458 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b96cac16078d282ee0924296817c6eee52196669 commit b96cac16078d282ee0924296817c6eee52196669 Author: Tom de Vries <tdevries@suse.de> Date: Wed Jun 21 16:16:50 2023 +0200 [gdb/testsuite] Fix gdb.tui/wrap-line.exp PR testsuite/30458 reports the following FAIL: ... PASS: gdb.tui/wrap-line.exp: width-auto-detected: cli: wrap ^CQuit (gdb) WARNING: timeout in accept_gdb_output Screen Dump (size 50 columns x 24 rows, cursor at column 6, row 3): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 W^CQuit 3 (gdb) ... FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap ... The problem is that the regexp doesn't account for the ^C: ... gdb_assert { [Term::wait_for "^WQuit"] } "prompt after wrap" ... The ^C occurs occasionally. This is something we'd like to fix. It's reported as a readline problem here ( https://lists.gnu.org/archive/html/bug-readline/2023-06/msg00000.html ). For now, fix this by updating the regexp, and likewise in another place in the test-case where we use ^C. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30458 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-21 14:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 15:07 [Bug gdb/30458] New: " simon.marchi at polymtl dot ca 2023-05-18 6:08 ` [Bug testsuite/30458] " vries at gcc dot gnu.org 2023-05-18 6:11 ` vries at gcc dot gnu.org 2023-05-21 16:02 ` vries at gcc dot gnu.org 2023-05-21 16:03 ` vries at gcc dot gnu.org 2023-05-21 16:09 ` vries at gcc dot gnu.org 2023-05-21 16:18 ` vries at gcc dot gnu.org 2023-05-21 16:21 ` vries at gcc dot gnu.org 2023-06-21 14:16 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-21 14:19 ` 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-30458-4717-o3WsLCfRnW@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).