From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Luis <luis.machado.foss@gmail.com>,
Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH] gdb/testsuite: make gdb.dwarf2/dw2-empty-inline-ranges.exp work when ASLR can't be disabled
Date: Thu, 5 Feb 2026 15:42:50 -0500 [thread overview]
Message-ID: <20260205204257.422150-1-simon.marchi@efficios.com> (raw)
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
---
gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp | 8 ++------
1 file changed, 2 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 ef75f642ac7d..16cd6ecbcfde 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-empty-inline-ranges.exp
@@ -56,11 +56,7 @@ 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.
if { [prepare_for_testing "failed to prepare" ${testfile} \
- [list ${srcfile}]] } {
- return -1
-}
-
-if {![runto_main]} {
+ [list ${srcfile}] {debug nopie}] } {
return -1
}
@@ -187,7 +183,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
}
base-commit: 458328833813d78831a0b1a24a0984db91c95fc0
--
2.53.0
next reply other threads:[~2026-02-05 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 20:42 Simon Marchi [this message]
2026-02-06 14:14 ` Andrew Burgess
2026-02-06 14:56 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260205204257.422150-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox