From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 7873) id 774F23858D39; Thu, 3 Mar 2022 03:30:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 774F23858D39 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Tiezhu Yang To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: testsuite: fix failed testcases in gdb.base/gdb-caching-proc.exp X-Act-Checkin: binutils-gdb X-Git-Author: Tiezhu Yang X-Git-Refname: refs/heads/master X-Git-Oldrev: e26ff4b5a90a67fc440052f6101464939347b1f2 X-Git-Newrev: cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f Message-Id: <20220303033023.774F23858D39@sourceware.org> Date: Thu, 3 Mar 2022 03:30:23 +0000 (GMT) X-BeenThere: gdb-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2022 03:30:23 -0000 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dcb1a6dda0d7b= 14034f647fbc48a7d6a2d212db7f commit cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f Author: Tiezhu Yang Date: Thu Mar 3 11:15:10 2022 +0800 gdb: testsuite: fix failed testcases in gdb.base/gdb-caching-proc.exp =20 When execute the following command: =20 make check-gdb TESTS=3D"gdb.base/gdb-caching-proc.exp" =20 we can see there exist some failed testcases: =20 FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 0: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 1: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 2: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 3: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 4: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 5: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 6: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 7: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 8: can spa= wn for attach (got interactive prompt) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 9: can spa= wn for attach (got interactive prompt) =20 here are the detailed messages in gdb/testsuite/gdb.log: =20 attach 873776 A program is being debugged already. Kill it? (y or n) n Not killed. (gdb) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 0: c= an spawn for attach (got interactive prompt) =20 so handle the case "A program is being debugged already. Kill it" in can_spawn_for_attach to fix the failed testcases. =20 Signed-off-by: Tiezhu Yang Diff: --- gdb/testsuite/lib/gdb.exp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 848cd080000..a35d08a05de 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -5130,6 +5130,10 @@ gdb_caching_proc can_spawn_for_attach { kill_wait_spawned_process $test_spawn_id return 1 } + -re "A program is being debugged already. Kill it. .y or n. " { + send_gdb "y\n" + exp_continue + } } =20 kill_wait_spawned_process $test_spawn_id