[Libunwind-devel] Patching the stack trace obtained by libunwind?

[Kirill Müller]

Hi


When developing for a script language that also supports native code 
(such as R or Python), it would be great to see an ensemble backtrace 
that contains source information in terms of the scripted language 
co-mingled with the native stack trace. One option to do this would be 
to support hooks that would patch the backtrace reported by libunwind. 
Would this be worthwhile exploring?

I don't know anything about libunwind's internals, a quick scan of its 
API and the last year's mailing list archives did not reveal anything in 
this direction. Thank you for a short feedback.


Best regards

Kirill