Pedro pointed out¹ that commit f5ef12c3f1af ("gdb/testsuite: Add libc_has_debug_info require helper") "[will] disable the testcase on systems that link with their libc statically (even if has debug info), or systems that name their libc something else." ¹ https://inbox.sourceware.org/gdb-patches/b0409c48-7f9c-4430-91d9-dc7cfa86a9c7@palves.net/
I posted a patch restoring the original test behaviour here: https://inbox.sourceware.org/gdb-patches/20240430015325.89780-1-thiago.bauermann@linaro.org/ Another alternative would be to revert commit f5ef12c3f1af. I would be ok with that.
I'm setting the 15.1 target milestone, because this one is a regression that seems to be in good tracks to be fixed quickly.
The master branch has been updated by Thiago Bauermann <bauermann@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=100318bcfda243f04cda3c29e8873c5710a1688a commit 100318bcfda243f04cda3c29e8873c5710a1688a Author: Thiago Jung Bauermann <thiago.bauermann@linaro.org> Date: Mon Apr 29 22:53:25 2024 -0300 gdb/testsuite: Restore libc_has_debug_info's less strict behaviour The code that was factored out from gdb.base/relativedebug.exp assumed that libc has debug info and only determined that it doesn't if it saw a specific message from GDB to that effect. In the process of factoring it into a require predicate, I made it stricter by trying to make a specific determination of whether or not debug info is available. Pedro noticed that "It'll disable the testcase on systems that link with their libc statically (even if has debug info), or systems that name their libc something else." Which is something I hadn't considered. This patch returns libc_has_debug_info to the original behaviour. Also, remove a verbose message that is redundant with the $message variable. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31700 Approved-By: Tom Tromey <tom@tromey.com>
IIUC this is fixed now.