https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128487
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Torbjorn SVENSSON from comment #0) > On arm-none-eabi, I see failures like: > > FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 execution test > FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++29 execution test > FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++23 execution test > FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++29 execution test > FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++23 execution test > FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++29 execution test > > The reason for the failures is that libbacktrace has no way to find the > symbols for the running embedded application. Is that just missing support in libbacktrace or a fundamental limitation of the target?
