Always destroy the process, regardless of its private state. This will call the virtual function DoDestroy under the hood, giving our derived class a chance to do the necessary tear down, including what to do when the private state is eStateExited.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This seems better to me. It's a little odd that the Process was short-cutting DoDestroy for these states. How can it know that one of the plugins might not need to handle that case? As an object lesson, that's true of eStateInvalid, which is the state you return with in the ProcessGDBRemote case when interrupting the stub fails, and that definitely needs cleanup.
Looks like the Windows plugin handles these cases already anyway, so this should be good.