diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-10-13 20:54:43 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-10-13 20:54:43 +0200 |
| commit | 54603750398b63263fd7924677ab0fe0affc4bad (patch) | |
| tree | eb22979cf64538fed3ec3ae2d1b5a2db10c9e330 /gdb/python/py-corefile.c | |
| parent | c0316a54b489d68e30de718aee69ab441799aad2 (diff) | |
| download | binutils-54603750398b63263fd7924677ab0fe0affc4bad.zip binutils-54603750398b63263fd7924677ab0fe0affc4bad.tar.gz binutils-54603750398b63263fd7924677ab0fe0affc4bad.tar.bz2 | |
[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
Diffstat (limited to 'gdb/python/py-corefile.c')
0 files changed, 0 insertions, 0 deletions