mono debug component not able to re-connect after disconnect #95256
Description
Description
Recently some rider user in our company reported to us that rider's mono remote debug tool is not able to re-connect to runtime debug component.
When looking into the component log, we found that rider will send a CMD_VM + CMD_VM_DISPOSE command set when disconnecting, while our custom visual studio debugger not (which is working fine).
According to pull request #67272 debugger-agent.c line 10463, if the debugger send this command set, the process function will reverse the bool check result, making the runtime skip the further debug thread restart code.
Compared to the previous version of this file, it seems the reverse is unnecessary, will you please check it? @thaystg
Reproduction Steps
- Enable mono debug component log with level equals or greater than 1, then start the mono runtime with debug enabled.
- using rider (rider EAP version is equal)'s mono remote debug tool to connect to the mono runtime's debug component
- stop the rider debug tool, while keep the mono runtime running.
- re-start the rider debug tool
Expected behavior
Expect rider's debug tool re-connect to mono debug component successfully.
Actual behavior
rider's debug tool is unable to re-connect, debug functions such as breakpoint event are not working as first launch.
Regression?
No response
Known Workarounds
If we remove the bool reverse we mentioned above and use the modified runtime, rider's debug tool re-connected as expect.
Configuration
No response
Other information
No response