diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-10-25 06:14:03 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-10-25 06:14:03 +0200 |
| commit | d4110830693458b6ec684b21e64ec6320a400f5b (patch) | |
| tree | ad08f3ad0c638a026b8c5ccea111ead367d6ede6 /gdb/testsuite/gdb.btrace | |
| parent | be6d665abddbdb598ca207472fbc37bb94799095 (diff) | |
| download | binutils-d4110830693458b6ec684b21e64ec6320a400f5b.zip binutils-d4110830693458b6ec684b21e64ec6320a400f5b.tar.gz binutils-d4110830693458b6ec684b21e64ec6320a400f5b.tar.bz2 | |
[gdb/testsuite] Fix some test-cases for check-read1 (gdb_test_lines)
I ran the testsuite in an environment simulating a stressed system in
combination with check-read1. This exposes a few more FAILs.
Fix some by using gdb_test_lines, as well as related gdb_get_lines.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/gdb.btrace')
| -rwxr-xr-x | gdb/testsuite/gdb.btrace/exception.exp | 25 |
1 files changed, 11 insertions, 14 deletions
diff --git a/gdb/testsuite/gdb.btrace/exception.exp b/gdb/testsuite/gdb.btrace/exception.exp index 61cc6c9..6ffdd2b 100755 --- a/gdb/testsuite/gdb.btrace/exception.exp +++ b/gdb/testsuite/gdb.btrace/exception.exp @@ -64,17 +64,14 @@ gdb_expect_list "flat" "\r\n$gdb_prompt $" [list \ ] # show the branch trace with calls indented -send_gdb "record function-call-history /c 1\n" -gdb_expect_list "indented" "\r\n$gdb_prompt $" [list \ - [multi_line \ - "1\tmain\\(\\)" \ - "2\t test\\(\\)" \ - "3\t foo\\(\\)" \ - "4\t bar\\(\\)" \ - "5\t bad\\(\\)\r" \ - ] "" \ - [multi_line \ - "\[0-9\]*\t test\\(\\)" \ - "\[0-9\]*\tmain\\(\\)" \ - ] "" \ - ] +gdb_test_lines "record function-call-history /c 1" \ + "indented" \ + [multi_line \ + "1\tmain\\(\\)" \ + "2\t test\\(\\)" \ + "3\t foo\\(\\)" \ + "4\t bar\\(\\)" \ + "5\t bad\\(\\)" \ + ".*" \ + "$decimal\t test\\(\\)" \ + "$decimal\tmain\\(\\)"] |