diff options
| author | Lancelot SIX <lancelot.six@amd.com> | 2022-10-07 14:44:40 +0100 |
|---|---|---|
| committer | Lancelot SIX <lancelot.six@amd.com> | 2022-10-07 20:15:21 +0100 |
| commit | ae17d05a4a58baf42f297dfd40ed29256f4bc44d (patch) | |
| tree | ada684bf75ad4cc13bf2884815e24e349faa582f /gdb | |
| parent | 7808a1f7f68cb38f66cf44bb91faae29b0dbfedd (diff) | |
| download | fsf-binutils-gdb-ae17d05a4a58baf42f297dfd40ed29256f4bc44d.zip fsf-binutils-gdb-ae17d05a4a58baf42f297dfd40ed29256f4bc44d.tar.gz fsf-binutils-gdb-ae17d05a4a58baf42f297dfd40ed29256f4bc44d.tar.bz2 | |
gdb/testsuite: fix gdb.threads/linux-dp.exp regex
On ubuntu 22.04 with the libc6-dbg package installed, I have the
following failure:
where
#0 print_philosopher (n=3, left=33 '!', right=33 '!') at .../gdb/testsuite/gdb.threads/linux-dp.c:105
#1 0x000055555555576a in philosopher (data=0x55555555937c) at .../gdb/testsuite/gdb.threads/linux-dp.c:148
#2 0x00007ffff7e11b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#3 0x00007ffff7ea3a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) FAIL: gdb.threads/linux-dp.exp: first thread-specific breakpoint hit
The regex for this test accounts for different situations (with /
without debug symbol) but assumes that if debug info is present the
backtrace shows execution under pthread_create. However, for the
implementation under test, we are under start_thread.
Update the regex to accept start_thread.
Tested on Ubuntu-22.04 x86_64 with and without libc6-dbg debug symbols
available.
Change-Id: I1e1536279890bca2cd07f038e026b41e46af44e0
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/testsuite/gdb.threads/linux-dp.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.threads/linux-dp.exp b/gdb/testsuite/gdb.threads/linux-dp.exp index 0805aa0..953e6a9 100644 --- a/gdb/testsuite/gdb.threads/linux-dp.exp +++ b/gdb/testsuite/gdb.threads/linux-dp.exp @@ -226,7 +226,7 @@ gdb_continue_to_breakpoint "thread 5's print" # If you do have debug info, the output obviously depends more on the # exact library in use; under NPTL, you get: # #2 0x0012b7fc in start_thread (arg=0x21) at pthread_create.c:264 -gdb_test "where" "print_philosopher.*philosopher.* \(from .*libpthread\|at pthread_create\|in pthread_create|from .*libc\\.\).*" \ +gdb_test "where" "print_philosopher.*philosopher.* \(from .*libpthread\|at pthread_create\|in pthread_create\|in start_thread\|from .*libc\\.\).*" \ "first thread-specific breakpoint hit" # Make sure it's catching the right thread. Try hitting the |