]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
[gdb/testsuite] Use expect_build_id_in_core_file a bit more
authorTom de Vries <tdevries@suse.de>
Mon, 13 Oct 2025 18:54:43 +0000 (20:54 +0200)
committerTom de Vries <tdevries@suse.de>
Mon, 13 Oct 2025 18:54:43 +0000 (20:54 +0200)
commit54603750398b63263fd7924677ab0fe0affc4bad
treeeb22979cf64538fed3ec3ae2d1b5a2db10c9e330
parentc0316a54b489d68e30de718aee69ab441799aad2
[gdb/testsuite] Use expect_build_id_in_core_file a bit more

Recent commit c1950dcc04c ("gdb/testsuite: fix failure from
gdb.python/py-corefile.exp") introduced proc expect_build_id_in_core_file,
which detects the problem that:
...
    ... some versions of the linker didn't place the build-id within the first
    page of an ELF.  As a result, the Linux kernel would not include the
    build-id in the generated core file, ...
...

Use this proc in a few more test-cases, to deal with the same problem.

Tested on x86_64-linux, openSUSE Tumbleweed with ld 2.43.1.

Approved-By: Andrew Burgess <aburgess@redhat.com>
PR testsuite/33528
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33528
gdb/testsuite/gdb.debuginfod/corefile-mapped-file.exp
gdb/testsuite/gdb.debuginfod/solib-with-soname.exp
gdb/testsuite/gdb.python/py-missing-objfile.exp