forked from Imagelibrary/binutils-gdb
0f2cd53cf4
On openSUSE Tumbleweed I run into this for the dwarf assembly test-cases, and
some hardcoded assembly test-cases:
...
Running gdb.dwarf2/fission-absolute-dwo.exp ...
gdb compile failed, ld: warning: fission-absolute-dwo.o: \
missing .note.GNU-stack section implies executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future \
version of the linker
=== gdb Summary ===
# of untested testcases 1
...
Fix the dwarf assembly test-cases by adding the missing .note.GNU-stack in
proc Dwarf::assemble.
Fix the hard-coded test-cases using this command:
...
$ for f in $(find gdb/testsuite/gdb.* -name *.S); do
if ! grep -q note.GNU-stack $f; then
echo -e "\t.section\t.note.GNU-stack,\"\",@progbits" >> $f;
fi;
done
...
Likewise for .s files, and gdb/testsuite/lib/my-syscalls.S.
The idiom for arm seems to be to use %progbits instead, see commit 9a5911c08b
("gdb/testsuite/gdb.dwarf2: Replace @ with % for ARM compatability"), so
hand-edit gdb/testsuite/gdb.arch/arm-disp-step.S to use %progbits instead.
Note that dwarf assembly testcases use %progbits as decided by proc _section.
Tested on x86_64-linux.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29674
23 lines
427 B
ArmAsm
23 lines
427 B
ArmAsm
.include "common.inc"
|
|
.include "arch.inc"
|
|
|
|
comment "Second file in assembly source debugging testcase."
|
|
|
|
.global foo2
|
|
gdbasm_declare foo2
|
|
comment "mark: foo2 start"
|
|
gdbasm_enter
|
|
|
|
comment "Call someplace else (several times)."
|
|
|
|
comment "mark: call foo3"
|
|
gdbasm_call foo3
|
|
gdbasm_call foo3
|
|
|
|
comment "All done, return."
|
|
|
|
comment "mark: foo2 leave"
|
|
gdbasm_leave
|
|
gdbasm_end foo2
|
|
.section .note.GNU-stack,"",@progbits
|