jade added a comment. In D62732#2789409 <https://reviews.llvm.org/D62732#2789409>, @sven wrote:
> It seems that the unwind didn't succeed, can you figure out the problem? > my qemu vesion: 4.2.1 > Thanks. Unfortunately, from my last adventures through the lldb codebase in debugging that (see bugs.llvm.org/show_bug.cgi?id=49941 for pertinent places to look at internals), that particular symptom may not provide enough detail to track this down to a root cause necessarily (in the case of missing this patch for instance, it would be that the debugger didn't know what the stack pointer was called). It could be that the patch is not applied, it could be something else entirely. I believe if you call Dump() with the debugger on an instance of one of the gdb protocol classes that has the register information (sorry, away from a computer and can't remember which one it is), you can see what registers it knows about. But overall our error reporting needs to be vastly improved on this case. I want to write a patch for it but I've not had the chance. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D62732/new/ https://reviews.llvm.org/D62732 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
