From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 99F213857004; Mon, 12 Sep 2022 14:45:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99F213857004
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1662993956;
	bh=gCYVG9K1/256u3S13xsKCwCJKtyUqbYlQlXXqH1aMxQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tHbMxNu4D54c2B2q1mEE9NcgI50cqQhqLg+KKexhpGpnSpRS/nY/ADkaXLqx/sN3c
	 z6b5cKcx+PXDSY3S0YZLrHWL8PDe4OdC3KjrCJOJ9oRh0YJ1pGlpwiD5K6s21ldsXf
	 jkhbyrsvME7Rkf6ewsRrkcaODxZL3x6nvYnMJeEg=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-27813-4717-CUV0c9nadJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27813-4717@http.sourceware.org/bugzilla/>
References: <bug-27813-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

--- 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 selfte=
st
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)=20
...

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 or=
der
seems correct.

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