On 6 September 2013 11:33, <[email protected]> wrote: > I do want to add some command that will inspect the current thread plans, so > you could see how they are stacked and cancel ones you don't care about > anymore. For instance, if you do: > > step over -> hit a breakpoint below on the stack > step over -> hit another breakpoint > > etc. Then if you continue, you'll finish the latest step over (unless you > hit another breakpoint in the process...) Then continue again will complete > the second step over. This is often quite convenient, but sometimes you just > want to forget about the step-over's and continue running. This would > provide a way to do that. Perhaps that would be a good place to insert some > info about how the plans will run the threads.
That would be perfect. I ended up adding a bunch of log Printfs to the thread plan functions in my tree in order to understand what was happening, including the stop_others value when pushing / queuing a sub plan. It might be handy to have the capability of querying the thread plans for a step / next without actually executing it as well. _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
