This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 68
PVSD should kill process when SIGHUP event is received #128
Comments
Wait, SIGHUP doesn't run atexit handlers? |
Also, I think the answer for VS would be that it doesn't get into such situations, because Windows doesn't have SIGHUP. I guess there's still a question of what remote debugging from VS would do, but I don't think we've ever tried that. |
Aaah yes, it doesn't have ANY signals.
Nope, from what I've read atexit handlers don't work for most signals. |
Merged
DonJayamanne
added a commit
that referenced
this issue
Feb 28, 2018
* exit on SIGHUP signal * Fixes #128
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@brettcannon @int19h @karthiknadig
Observed behaviour:
termainted
eventProposed solution
terminated
event from within and exit the process.The reason I'm proposing this is because its better for PTVSD to send messages directly to VS Code where possible (avoid need for VS Code adapter to do the dirty work of figuring out when to send terminated events, etc).
@karthiknadig how does VS handle such situations (closing terminal)?
Is this where you too are handling the
error
andclose
events of the socket connection?The text was updated successfully, but these errors were encountered: