diff options
| author | Tiezhu Yang <yangtiezhu@loongson.cn> | 2022-03-03 11:15:10 +0800 |
|---|---|---|
| committer | Tiezhu Yang <yangtiezhu@loongson.cn> | 2022-03-03 11:28:09 +0800 |
| commit | cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f (patch) | |
| tree | fc04093cdba3bb6d4fa85c16ece5c78879cedd87 | |
| parent | e26ff4b5a90a67fc440052f6101464939347b1f2 (diff) | |
| download | gdb-cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f.zip gdb-cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f.tar.gz gdb-cb1a6dda0d7b14034f647fbc48a7d6a2d212db7f.tar.bz2 | |
gdb: testsuite: fix failed testcases in gdb.base/gdb-caching-proc.exp
When execute the following command:
make check-gdb TESTS="gdb.base/gdb-caching-proc.exp"
we can see there exist some failed testcases:
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 0: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 1: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 2: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 3: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 4: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 5: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 6: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 7: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 8: can spawn for attach (got interactive prompt)
FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 9: can spawn for attach (got interactive prompt)
here are the detailed messages in gdb/testsuite/gdb.log:
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: can spawn for attach (got interactive prompt)
so handle the case "A program is being debugged already. Kill it" in
can_spawn_for_attach to fix the failed testcases.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
| -rw-r--r-- | gdb/testsuite/lib/gdb.exp | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 848cd08..a35d08a 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 + } } kill_wait_spawned_process $test_spawn_id |