https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128487
--- Comment #2 from Torbjorn SVENSSON <azoff at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #1) > (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? I'd say it's sort of both. In an embedded target, only the actual application instructions, literal pools, etc are available, not the symbol table. So, without the symbol table, how would a symbol be looked up? I do not think this is unique to arm-none-eabi targets, but should probably be applicable to all embedded targets that do not have any OS.
