On 11/9/13, 10:01 AM, Richard Weinberger wrote:
The DWARF2-EH unwinder was dropped from mainline years ago .
Commit d1526e2c (Remove stack unwinder for now)
Why does the openSUSE kernel still carry this unwinder?
We carry it in our kernels because the benefits far outweigh the costs
in maintaining it ourselves. The in-kernel unwinder uses some heuristics
to determine what is or isn't a kernel address and products stack traces
of questionable veracity. The DWARF unwinder products much more accurate
traces and it's not too invasive to integrate into our kernels.
If all problems have been resolved please push it back
The patches, mostly in the vein of annotations, have been flowing
upstream gradually. The reasons for it not being included last time were
due to Linus objecting to the unwinder accessing stack data and assuming
it was trusted. I'm not sure if those objections have been addressed yet.