jingham added a comment. "Unwinding" the zero-th frame is really just getting the PC & FP. Since you are very likely to need this information on any given stop, lldb has accelerated versions of the gdb-remote stop reply packets that provide this information up front so this sort of request is cheap to fulfill. I know that debugserver & lldbserver both provide these accelerated stop-reply packet. If you are using either of these debug stubs, this shouldn't be a performance problem. Are you using a different stub, and if so and you can switch to using the lldb-server stub - or fixing your stub to provide the accelerated stop reply packets, your lldb sessions will be a lot more efficient...
CHANGES SINCE LAST ACTION https://reviews.llvm.org/D103271/new/ https://reviews.llvm.org/D103271 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
