mstorsjo added a comment. In D67954#1707791 <https://reviews.llvm.org/D67954#1707791>, @labath wrote:
> Hard to say off-hand, but the first thing I'd check is whether the > information about loaded modules and their addresses is making its way into > lldb. You can use the "image list" command to inspect that. Then there's the > "image show-unwind" command which can show you how lldb will try to unwind > for a given function/address. Also, if you enable the "unwind" log channel > (log enable lldb unwind), you'll get a trace of what lldb did while > attempting to unwind. Thanks for the debugging pointers. I managed to track this down, with a fix suggestion in D68939 <https://reviews.llvm.org/D68939>. I guess that indicates another issue elsewhere, but it's pretty much out of scope for me to dig further into that issue now. I guess it should be possible to reproduce the same issue on x86_64 by changing the triple similarly there as well. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D67954/new/ https://reviews.llvm.org/D67954 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
