diff options
| author | Bratislav Filipovic <bfilipov@amd.com> | 2026-04-03 08:11:02 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2026-04-03 08:11:02 +0200 |
| commit | 5ae26f34ef5ac863203d63fffc968d63e823172f (patch) | |
| tree | 89b55d6d903982a8d882e5d35b813355227cb57c /binutils | |
| parent | 297cd3f78b491c65f05580d78195e5f361fb1a28 (diff) | |
| download | fsf-binutils-gdb-5ae26f34ef5ac863203d63fffc968d63e823172f.tar.gz fsf-binutils-gdb-5ae26f34ef5ac863203d63fffc968d63e823172f.tar.bz2 fsf-binutils-gdb-5ae26f34ef5ac863203d63fffc968d63e823172f.zip | |
testsuite: ada-valprint-error relocation issue
The ada-valprint-error.exp test links a nodebug .o file with a separate
DWARF .o file generated by lib/dwarf.exp. This requires the linker to
apply relocations for initialized pointers in the .data section.
Some clang + linker combinations fail to apply these relocations,
leaving fd__global as NULL instead of pointing to buffer. This causes
the test to print null instead of the expected error message.
Binary evidence from .comment section confirms which compiler and
linker were used. Testing shows:
- GCC 13 + GNU ld 2.42: PASS
- clang 20 + GNU ld 2.42: FAIL
- clang 22 + ld.lld 22: FAIL
- clang 17/19 + GNU ld 2.45.0: PASS
The failure is a linker limitation when handling this specific
relocation pattern, not a GDB bug. Document this in the test file
to help users understand why the test may fail with certain toolchains.
Approved-By: Tom de Vries <tdevries@suse.de>
Diffstat (limited to 'binutils')
0 files changed, 0 insertions, 0 deletions