John David Anglin wrote:
I started looking into why CONFIG_BACKTRACE_SELF_TEST=y shows uncomplete/wrong/broken backtraces.
To me it seems, that the unwind tables are broken when using newer gcc/binutils versions.
Just wondering, but would it be possible to switch to using dwarf2 unwind
information. I presume that's what most other targets use.
the hppa kernel unwinder is derived from the ia64 unwinder, which is not
dwarf2 based.
The only dwarf references I find in the kernel are some dwarf markups in
signal frames to help userspace with signal frame unwinding. Have I
missed anything?
x86 seems to do something very ad-hoc.
randolph
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html