This is an archive of the discontinued LLVM Phabricator instance.

Use Resume not PrivateResume when asynchronously continuing after the start at stop
ClosedPublic

Authored by jingham on Feb 23 2023, 12:09 PM.

Details

Summary

In the auto-continue after we stop at the start point when running the debugger asynchronously, we use PrivateResume to continue. But that doesn't update the stop locker state, which is currently at "stopped". That means the stop locker wasn't doing its job to prevent you from running expressions while the target is running.

I fixed this, and added a test for this case to make sure we get a proper error back. This patch requires (and adds the test for):

https://reviews.llvm.org/D144664

Diff Detail

Event Timeline

jingham created this revision.Feb 23 2023, 12:09 PM
Herald added a project: Restricted Project. · View Herald TranscriptFeb 23 2023, 12:09 PM
jingham requested review of this revision.Feb 23 2023, 12:09 PM
Herald added a project: Restricted Project. · View Herald TranscriptFeb 23 2023, 12:09 PM
This revision was not accepted when it landed; it landed in state Needs Review.Feb 28 2023, 5:35 PM
This revision was automatically updated to reflect the committed changes.

Looks like the new test is failing on the windows lldb bot: https://lab.llvm.org/buildbot/#/builders/83/builds/29680. The buildbot was already red because of TestCommandScript.py, so you might have missed this.

mib added a subscriber: mib.Mar 27 2023, 12:54 PM
mib added inline comments.
lldb/test/API/python_api/run_locker/TestRunLocker.py
25

@jingham, you're testing the same thing twice. You probably wanted to set the stop_at_entry argument to True here.