jasonmolenda accepted this revision.
jasonmolenda added a comment.
This revision is now accepted and ready to land.
Sorry yes, I should have marked this as approved. I don't have a linux machine
handy so I haven't looked into the problem Jan reports with the change -- fwiw
if you turn on unwind logging ('log enable lldb unwind' before you backtrace at
a stop), it will tell you which unwind rule it is using to find the caller's
return pc value as it goes up the stack. It's a little tricky to read at
first, but once you get the hang of it you can usually spot the problem quickly
and understand why lldb is behaving the way it is. But just looking at the
source changes you're making, I'm fine with this.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D63667/new/
https://reviews.llvm.org/D63667
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
