Skip to content

DebuggerState refector #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
xusheng6 opened this issue Dec 21, 2021 · 2 comments
Closed

DebuggerState refector #105

xusheng6 opened this issue Dec 21, 2021 · 2 comments

Comments

@xusheng6
Copy link
Member

Refine the signatures of the interface functions, most notably the target control functions, e.g., SingleStep(). Also remember to define its semantic, i.e., whether it should return immediately, or it should return when the target stops for the first time.

@xusheng6 xusheng6 added this to the Stable version milestone Dec 21, 2021
@xusheng6
Copy link
Member Author

This is mostly done. After various experiments, I have decided that a synchronous execution model is better suited for us. This differs from the decision made by VSCode or Visual studio. It is closer to that of windbg. I still make heavy use of debugger events to notify the change of the debugger status.

@xusheng6
Copy link
Member Author

xusheng6 commented Jan 17, 2022

Also, the DebuggerState's role is downgraded to a collection of cached information of the debugger. The control related functionalities are moved into the DebuggerController class, which is the core of the debugger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant