Files
binutils-gdb/gdb/testsuite/gdb.threads/pthread_cond_wait.exp
Tom de Vries 2bcfdb758b [gdb/testsuite] Handle PAC marker
On aarch64-linux, I run into:
...
FAIL: gdb.base/annota1.exp: backtrace from shlibrary (timeout)
...
due to the PAC marker showing up:
...
^Z^Zframe-address^M
0x000000000041025c [PAC]^M
^Z^Zframe-address-end^M
...

In the docs the marker is documented as follows:
...
When GDB is debugging the AArch64 architecture, and the program is using the
v8.3-A feature Pointer Authentication (PAC), then whenever the link register
$lr is pointing to an PAC function its value will be masked.  When GDB prints
a backtrace, any addresses that required unmasking will be postfixed with the
marker [PAC].  When using the MI, this is printed as part of the addr_flags
field.
...

Update the test-case to allow the PAC marker.

Likewise in a few other test-cases.

While we're at it, rewrite the affected pattern pat_begin in annota1.exp into
a more readable form.  Likewise for the corresponding pat_end.

Tested on aarch64-linux.

Approved-By: Luis Machado <luis.machado@arm.com>

PR testsuite/31202
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31202
2024-01-04 13:42:45 +01:00

65 lines
2.2 KiB
Plaintext

# Copyright (C) 2004-2023 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Please email any bugs, comments, and/or additions to this file to:
# bug-gdb@gnu.org
# This file verifies that GDB is able to compute a backtrace for a thread
# being blocked on a call to pthread_cond_wait().
standard_testfile
if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable debug] != "" } {
return -1
}
clean_restart ${binfile}
runto_main
gdb_test "break break_me" \
"Breakpoint 2 at .*: file .*${srcfile}, line .*" \
"breakpoint on break_me"
gdb_test "continue" \
".*Breakpoint 2, break_me ().*" \
"run to break_me"
#
# Backtrace all threads, find the one running noreturn, and
# verify that we are able to get a sensible backtrace, including
# the frame for the pthread_cond_wait() call.
#
# The string below will only match if the functions named
# occur in a single thread's backtrace, in the given order.
#
global hex
global decimal
#
# This is a "backtrace break" ("btb"):
#
set btb "\[^\r\n\]+\[\r\n\]+\#${decimal}\[ \t\]+${hex} (\\\[PAC\\\] )?in "
# One of the threads is blocked on a call to pthread_cond_wait, and
# we want to verify that we are able to get a sensible backtrace for
# that thread. Because we don't know its thread ID, we can't switch
# to it before doing the backtrace. So we get a backtrace for all
# threads, and verify that one them returns the expected backtrace.
gdb_test "thread apply all backtrace" \
"pthread_cond_wait${btb}cond_wait${btb}noreturn${btb}forever_pthread.*" \
"backtrace in blocked thread"