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 gdb/27813] FAIL: gdb.linespec/cpcompletion.exp: incomplete-scope-colon: tab complete "b cpls.cc:'ns_incomplete_scope_colon_test::i" (clearing input line) (timeout) Date: Mon, 12 Sep 2022 14:45:56 +0000 [thread overview] Message-ID: <bug-27813-4717-CUV0c9nadJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27813-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27813 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- I minimized to: ... $ cat gdb/testsuite/gdb.gdb/unittest.exp set bell_re "\\\x07" set n 1000 for {set i 0} {$i < $n} {incr i} { with_test_prefix $i { clean_restart set cmd "maintenance selftest name_that_does_not_exist" set test "test_completion: tab complete \"$cmd\"" send_gdb "$cmd\t" gdb_test_multiple "" "$test" { -re "$cmd$bell_re$" { pass $gdb_test_name } } send_gdb "\003" gdb_test_multiple "" "$test (clearing input line)" { -re "Quit\r\n$gdb_prompt $" { } } send_gdb "\n" gdb_test_multiple "" "$test (enter)" { -re "\r\n$gdb_prompt $" { } } } } ... and am able to reproduce the FAIL by running the test-case with taskset -c 0. I added the "\n" bit to get an idea of what happens after the timeout, and got: ... (gdb) maintenance selftest name_that_does_not_exist^GPASS: gdb.gdb/unittest.exp: 59: test_completion: tab complete "maintenance selftest name_that_does_not_exist" FAIL: gdb.gdb/unittest.exp: 59: test_completion: tab complete "maintenance selftest name_that_does_not_exist" (clearing input line) (timeout) ^C^M Ran 0 unit tests, 0 failed^M (gdb) Quit^M (gdb) ... This seems like what would happen if we'd first do \n, and then ^C. AFAICT, the terminal echoes first ^C, then the \n, so at least there the order seems correct. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-12 14:45 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 13:28 [Bug gdb/27813] New: " vries at gcc dot gnu.org 2021-05-03 23:21 ` [Bug gdb/27813] " vries at gcc dot gnu.org 2022-04-06 21:05 ` vries at gcc dot gnu.org 2022-04-06 21:17 ` simark at simark dot ca 2022-09-12 9:02 ` luis.machado at arm dot com 2022-09-12 14:45 ` vries at gcc dot gnu.org [this message] 2022-09-12 15:02 ` vries at gcc dot gnu.org 2022-09-12 15:48 ` vries at gcc dot gnu.org 2022-09-13 6:57 ` vries at gcc dot gnu.org 2022-09-13 7:40 ` vries at gcc dot gnu.org 2022-09-13 7:41 ` vries at gcc dot gnu.org 2022-09-13 12:57 ` vries at gcc dot gnu.org 2022-09-16 13:58 ` vries at gcc dot gnu.org 2023-05-24 9:20 ` [Bug cli/27813] " vries at gcc dot gnu.org 2023-05-24 9:41 ` vries at gcc dot gnu.org 2023-05-24 9:42 ` vries at gcc dot gnu.org 2023-05-24 10:42 ` vries at gcc dot gnu.org 2023-06-07 12:57 ` cvs-commit at gcc dot gnu.org 2023-06-14 5:51 ` 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-27813-4717-CUV0c9nadJ@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).