mstorsjo added a comment. In D67954#1707791 <https://reviews.llvm.org/D67954#1707791>, @labath wrote:
> Thank you _very_ much for those tests. +@mgorny, in case he has any comments > on those. > > In D67954#1707292 <https://reviews.llvm.org/D67954#1707292>, @mstorsjo wrote: > > > The tests pass both with and without use of lldb-server. However, when > > using lldb-server with NativeRegisterContext, while the register values are > > correct, I don't get a correct working backtrace with it. Without > > lldb-server, I get a perfect backtrace. (The tested binary uses SEH unwind > > tables, but DWARF debug info.) Any clues about what might be going wrong > > there? > > > 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 tips. When I run `image list` I get `error: the target has no associated executable images`, so that pretty clearly shows that something's missing. On x86_64, `image list` shows only the debugged exe itself, when run with `LLDB_USE_LLDB_SERVER=1`, while it shows the exe and a few system dlls (ntdll, kernel32, kernelbase and ucrtbase) when run without lldb-server. 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
