binutils-gdb/gdb/testsuite/gdb.btrace/rn-dl-bind.exp
Markus Metzger 8233378104 gdb, testsuite: enforce lazy binding for gdb.btrace/rn-dl-bind.exp
In gdb.btrace/rn-dl-bind.exp we test that we can reverse-step over
recorded dynamic linking.  The test covers specific behaviour to support
_dl_runtime_resolve calling the resolved function by returning to it.
This would normally mess up stepping as we'd end up with backtraces that
contain the same functions but different frame ids.

Since GDB needs to recognize a return from _dl_runtime_resolve, the test
only passes when debug information for _dl_runtime_resolve is available.

The test requires that symbols are bound lazily.  Otherwise, we won't
record dynamic linking and the test will be fairly pointless.

Recent GCC pass -z now by default to bind symbols eagerly.  Add -z lazy to
the test's ldflags to enforce lazy binding.
2021-03-03 09:18:58 +01:00

67 lines
2.0 KiB
Plaintext

# This testcase is part of GDB, the GNU debugger.
#
# Copyright 2013-2021 Free Software Foundation, Inc.
#
# Contributed by Intel Corp. <markus.t.metzger@intel.com>
#
# 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/>.
#
#
# Test that we can reverse-next over the dynamic linker's symbol
# lookup code.
if { [skip_btrace_tests] } {
unsupported "target does not support record-btrace"
return -1
}
standard_testfile
if [prepare_for_testing "failed to prepare" $testfile $srcfile \
{c++ debug ldflags=-Wl,-z,lazy}] {
return -1
}
if ![runto_main] {
untested "failed to run to main"
return -1
}
# trace the code for the call to test
gdb_test_no_output "record btrace"
gdb_test "next" ".*main\.2.*"
# just dump the function-call-history to help debugging
gdb_test_no_output "set record function-call-history-size 0"
gdb_test "record function-call-history /cli 1" ".*"
# check that we can reverse-next and next
with_test_prefix "main" {
gdb_test "reverse-next" ".*main\.1.*"
gdb_test "next" ".*main\.2.*"
}
# now go into test and try to (reverse-)next over the library call
#
# reverse-stepping through the epilogue is not very reliable; depending on
# debug information we may stop at the closing brace or at the return.
#
# instead, run to test
gdb_breakpoint test {temporary}
gdb_test "reverse-continue" ".*test\.1.*"
with_test_prefix "test" {
gdb_test "next" ".*test\.2.*"
gdb_test "reverse-next" ".*test\.1.*"
}