public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30458] New: FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap Date: Wed, 17 May 2023 15:07:11 +0000 [thread overview] Message-ID: <bug-30458-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30458 Bug ID: 30458 Summary: FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at polymtl dot ca Target Milestone: --- I sometimes see this failure on my CI. This time, it was with the native-gdbserver board, not sure if it matters (maybe it does for timing). I haven't been able to reproduce it locally yet. Here's a snippet from gdb.log maint info screen Number of characters gdb thinks are in a line is 50. Number of characters readline reports are in a line is 49. Number of characters curses thinks are in a line is 50. Number of characters environment thinks are in a line is 50 (COLUMNS). Number of lines gdb thinks are in a page is 4294967295 (unlimited). Number of lines readline reports are in a page is 32767 (unlimited). Number of lines curses thinks are in a page is 24. Number of lines environment thinks are in a page is 24 (LINES). (gdb) PASS: gdb.tui/wrap-line.exp: width-auto-detected: maint info screen PASS: gdb.tui/wrap-line.exp: width-auto-detected: width PASS: gdb.tui/wrap-line.exp: width-auto-detected: $gdb_width == [expr $readline_width + 1] Quit (gdb) PASS: gdb.tui/wrap-line.exp: width-auto-detected: cli: start line 7890123456789012345678901234567890123456789 WBox Dump (50 x 24) @ (0, 0): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Box Dump (50 x 24) @ (0, 0): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Box Dump (50 x 24) @ (0, 0): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Box Dump (50 x 24) @ (0, 0): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Box Dump (50 x 24) @ (0, 0): 0 Quit 1 (gdb) 7890123456789012345678901234567890123456789 2 W 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 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) 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-05-17 15:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 15:07 simon.marchi at polymtl dot ca [this message] 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 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@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).