This shouldn't require any extra effort, however, since the "step out breakpoint" set in the ThreadPlanStepOut is set as thread specific for that thread. If a thread specific breakpoint is hit by a different thread, the process is just auto-continued without notifying the thread of the stop. And in fact, the stop reason of that thread is set to nothing so if you happen to hit a thread specific breakpoint on two threads simultaneously, only the one set for that breakpoint will see a stop reason of "breakpoint hit". So the correct behavior should obtain automatically. If it doesn't it means something about thread specific breakpoints is broken.
Jim On Sep 18, 2013, at 3:43 PM, [email protected] wrote: > Step out breakpoints are always thread specific, since they implement > operations for one specific thread. So conceptually there is no breakpoint > at the step out destination for thread B, though in practice this means if > thread B hits the step out breakpoint it should continue without stopping. > Is this not working? > > Jim > > On Sep 18, 2013, at 3:37 PM, Kopec, Matt <[email protected]> wrote: > >> Hi Jim, >> >> A question came up about the correct behavior when a thread hits a step-out >> breakpoint that was intended for another thread. >> >> In the TestThreadStepOut test case, two threads are stopped inside the same >> function (invoked from the same call site) and Thread A is issued a ‘thread >> step-out –m all-threads’. What should happen if Thread B hits the step-out >> breakpoint before Thread A? Should Thread B continue past the breakpoint or >> stop there until Thread A finishes the step-out? >> >> Thanks, >> Matt > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
