Hi,
* in order to have the android's debuggerd use libunwind I looked at
libunwind's remote interface and especially the libunwind-ptrace lib
that sits on top of that.
* the remote interface seems a bit awkward to me. The user provides
a set of callbacks to access the inferior memory or registers. Instead
of using these callbacks to obtain the actual unwind information
(eh_frame fro example) it requires the user implement another callback
(find_proc_info) to lookup the unwind info himself.
* the libunwind-ptrace currently deos not support the ARM specific
unwind tables
* started to look into how to improve the situation
* not straight forward as it's tightly bound to eh_frame unw info
and libunwinds DWARF parsing mechanism
* attending a class this afternoon
* Note: I'm on vacation starting in a few hours and I'll be back on
Tuesday next week.
Regards
Ken
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
