https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117941
--- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- > Is it then possible to have dwarf data on ARM in addition to the EABI defined > unwind section? I don't know, honesty, because I've not tried it. I'd be surprised if it worked though, at least, not without hacking the linker scripts. The dwarf data normally lives in the debug sections, which aren't loaded when the binary is executed (it's just available to a debugger). The original version of the EABI specification did not support a frame chain, but this was added as an option in the recent versions. This would enable a (nearly) complete backtrace of the call stack without needing other data (just access to the symbol table). Sadly, however, this is yet to be implemented in gcc (the existing code doesn't correctly support thumb and certainly doesn't support Arm and thumb together in the same binary.
