From deb47060b5812c6c41ecc790cb28898fcbc45c93 Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Thu, 5 Feb 2026 15:42:50 -0500 Subject: [PATCH] gdb/testsuite: make gdb.dwarf2/dw2-empty-inline-ranges.exp work when ASLR can't be disabled A colleague that goes by the name "Luis Machado" reported a failure when running gdb.dwarf2/dw2-empty-inline-ranges.exp. After investigation, we found that the conditions for the test to fail are: - running in an environment where GDB can't disable address space randomization (such as in a container where that capability is removed) - a toolchain generating position-independent executables The test does a first run to grab the addresses of a few labels defined in the source file. It then crafts the DWARF using these addresses. And then it does a second run for the actual test stuff. When the executable is PIE and ASLR is active, then the addresses in both runs don't agree, which the test doesn't expect. It is possible to emulate the failure by inserting some: gdb_test_no_output "set disable-randomization off" after both "prepare_for_testing" calls. The (first) failure then manifests as: FAIL: gdb.dwarf2/dw2-empty-inline-ranges.exp: dwarf_version=4: empty_loc=start: entry_pc_type=empty: stopped at entry-pc This test compares the expected stop PC "entry_pc" with the actual stop PC "pc". In my example run, they were indeed different: pc = 0x5603ec67a159 entry_pc = 0x55baba6a9159 The simplest way to fix this, which this patch implements, is to use "nopie" when building the binaries. I don't think this affects the effectiveness of the test. Also, in the first run, it is longer necessary to run the inferior before grabbing the addresses, they are going to be the same with a non-PIE executable. So remove that. Change-Id: I3e9b1c056c30a49e01e1a1d3bf28f7e0e409f3c9 Approved-By: Andrew Burgess --- gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp b/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp index ef75f642ac7..a3c88d950f8 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp @@ -55,12 +55,11 @@ get_func_info main # Compile the source file and load the executable into GDB so we can # extract some addresses needed for creating the DWARF. +# +# Use `nopie` to ensure that addresses are the same across runs, in case ASLR +# can't be disabled. if { [prepare_for_testing "failed to prepare" ${testfile} \ - [list ${srcfile}]] } { - return -1 -} - -if {![runto_main]} { + [list ${srcfile}] {debug nopie}] } { return -1 } @@ -187,7 +186,7 @@ proc run_test { dwarf_version empty_loc entry_pc_type } { write_asm_file $asm_file $dwarf_version $ranges $entry_pc_label if {[prepare_for_testing "failed to prepare" $this_testfile \ - [list $::srcfile $asm_file] {nodebug}]} { + [list $::srcfile $asm_file] {nodebug nopie}]} { return } -- 2.47.3