Re: [PATCH v5 5/5] gdb/testsuite: Test for a backtrace through object without debuginfo

Thiago Jung Bauermann
2024-10-03T02:48:43Z

Guinevere Larsen <guinevere@redhat.com> writes:

> From: Guinevere Larsen <blarsen@redhat.com>
>
> Fedora has been carrying this test since back in the Project Archer
> days. A change back then caused GDB to stop being able to backtrace when
> only some of the object files had debug information. Even though the
> changed code never seems to have made its way into the main GDB project,
> I think it makes sense to bring the test along to ensure something like
> this doesn't pass unnoticed.
>
> Co-Authored-By: Jan Kratochvil <jan@jankratochvil.net>
> ---
> .../backtrace-through-cu-nodebug-caller.c | 28 ++++++
> .../backtrace-through-cu-nodebug-main.c | 32 +++++++
> .../gdb.base/backtrace-through-cu-nodebug.exp | 90 +++++++++++++++++++
> 3 files changed, 150 insertions(+)
> create mode 100644 gdb/testsuite/gdb.base/backtrace-through-cu-nodebug-caller.c
> create mode 100644 gdb/testsuite/gdb.base/backtrace-through-cu-nodebug-main.c
> create mode 100644 gdb/testsuite/gdb.base/backtrace-through-cu-nodebug.exp

Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>

--
Thiago