Re: [Lldb-commits] [lldb] r332922 - Work around some odd instruction single-step behavior on macOS.

> > On May 22, 2018, at 9:37 AM, Jim Ingham wrote: > > > > I haven't played around with this yet. Can it also provide enough memory to pretend a stack trace? Most of the thread plan stuff will fall over pretty early if it doesn't have at least a couple of frames? You can do

Re: [Lldb-commits] [lldb] r332922 - Work around some odd instruction single-step behavior on macOS.

BTW, I think it is likely that we are being interrupted, but the bug happens very infrequently and generally goes away when I turn on more than a trivial amount of logging, so it's been hard to prove that yet. Jim > On May 22, 2018, at 9:37 AM, Jim Ingham wrote: > > I

Re: [Lldb-commits] [lldb] r332922 - Work around some odd instruction single-step behavior on macOS.

I haven't played around with this yet. Can it also provide enough memory to pretend a stack trace? Most of the thread plan stuff will fall over pretty early if it doesn't have at least a couple of frames? Jim > On May 22, 2018, at 2:41 AM, Pavel Labath wrote: > > This

Re: [Lldb-commits] [lldb] r332922 - Work around some odd instruction single-step behavior on macOS.

This probably isn't what was happening here because you would have seen the extra stops in the logs, but one way I can think of we can end up at the same PC is if the process gets a signal while we're about to single-step it, in which case we need to execute the signal handler first and then get

[Lldb-commits] [lldb] r332922 - Work around some odd instruction single-step behavior on macOS.

Author: jingham Date: Mon May 21 17:06:55 2018 New Revision: 332922 URL: http://llvm.org/viewvc/llvm-project?rev=332922=rev Log: Work around some odd instruction single-step behavior on macOS. We've seen some cases on macOS where you go to instruction single step (over a breakpoint), and single