The previous diff (and it's subsequent fix) were reverted as the tests didn't work properly on the AArch64 & ARM LLDB buildbots. I made a couple more minor changes to tests (from @clayborg's feedback) and disabled them for non Linux-x86(_64) builds, as I don't have the ability do anything about an ARM64 Linux failure. If I had to guess, I'd say the toolchain on the buildbots isn't respecting the `-Wl,--build-id` flag. Maybe, one day, when I have a Linux AArch64 system I'll dig in to it. From the reverted PR: I've migrated the tests in my https://github.com/llvm/llvm-project/pull/79181 from shell to API (at @JDevlieghere's suggestion) and addressed a couple issues that were exposed during testing. The tests first test the "normal" situation (no DebugInfoD involvement, just normal debug files sitting around), then the "no debug info" situation (to make sure the test is seeing failure properly), then it tests to validate that when DebugInfoD returns the symbols, things work properly. This is duplicated for DWP/split-dwarf scenarios. --------- Co-authored-by: Kevin Frei <freik@meta.com>
20 lines
492 B
Makefile
20 lines
492 B
Makefile
C_SOURCES := main.c
|
|
|
|
# For normal (non DWP) Debuginfod tests, we need:
|
|
|
|
# * The full binary: a.out.unstripped
|
|
# Produced by Makefile.rules with SAVE_FULL_DEBUG_BINARY set to YES and
|
|
# SPLIT_DEBUG_SYMBOLS set to YES
|
|
|
|
# * The stripped binary (a.out)
|
|
# Produced by Makefile.rules with SPLIT_DEBUG_SYMBOLS set to YES
|
|
|
|
# * The 'only-keep-debug' binary (a.out.debug)
|
|
# Produced below
|
|
|
|
SPLIT_DEBUG_SYMBOLS := YES
|
|
SAVE_FULL_DEBUG_BINARY := YES
|
|
GEN_GNU_BUILD_ID := YES
|
|
|
|
include Makefile.rules
|