On 09/16/2011 06:31 PM, Arun Sharma wrote:
On Thu, Sep 15, 2011 at 12:47 AM, Ken Werner<[email protected]> wrote:
Exactly. I've ported libunwind to work on Android and hacked the debuggerd
to make use of libunwind-ptrace to dump stack traces. The other reason I
wanted a libunwind with remote unwinding capabilities only is that bionic
(Androids libc) doesn't support dl_iterate_phdr which would be essential for
local unwinding.
A standalone async signal safe dl_iterate_phdr() with minimal hooks
may not be such a bad thing :)
I agree. :)
Yeah -DUNW_REMOTE_ONLY looks good to me.
Since libunwind-ptrace is using the remote interface I had to tweak the
sources a bit. The patches can be found at:
http://lists.nongnu.org/archive/html/libunwind-devel/2011-10/msg00020.html
Regards
Ken
_______________________________________________
Libunwind-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/libunwind-devel
