Python VS Code Debug - Capture SIGTERM?
I'd like to force sys.exit()
when the python debugger is stopped. When I stop the debugger I see Terminated: 15
so I assume this is SIGTERM
. However, when stopping the debugger, my kill function isn't called.
def kill(sig, frame):
sys.exit(0)
signal.signal(signal.SIGINT, kill)
signal.signal(signal.SIGTERM, kill)
When stopping the vscode debugger, what signal is sent?
Edit:
Just tried all of them. No love
for s in signal.Signals:
try:
signal.signal(s, self._kill)
except:
pass
python visual-studio-code
add a comment |
I'd like to force sys.exit()
when the python debugger is stopped. When I stop the debugger I see Terminated: 15
so I assume this is SIGTERM
. However, when stopping the debugger, my kill function isn't called.
def kill(sig, frame):
sys.exit(0)
signal.signal(signal.SIGINT, kill)
signal.signal(signal.SIGTERM, kill)
When stopping the vscode debugger, what signal is sent?
Edit:
Just tried all of them. No love
for s in signal.Signals:
try:
signal.signal(s, self._kill)
except:
pass
python visual-studio-code
SIGHUP
orSIGSEGV
orSIGSTOP
?
– Torxed
Nov 15 '18 at 18:05
@Torxed no luck
– micah
Nov 15 '18 at 18:06
How about this to see if anything triggers? Edited my first comment, I think it'sSIGSTOP
if anything.
– Torxed
Nov 15 '18 at 18:07
Have you added a print statement or something to your kill function, or tried executing it withpython -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).
– Torxed
Nov 15 '18 at 18:25
add a comment |
I'd like to force sys.exit()
when the python debugger is stopped. When I stop the debugger I see Terminated: 15
so I assume this is SIGTERM
. However, when stopping the debugger, my kill function isn't called.
def kill(sig, frame):
sys.exit(0)
signal.signal(signal.SIGINT, kill)
signal.signal(signal.SIGTERM, kill)
When stopping the vscode debugger, what signal is sent?
Edit:
Just tried all of them. No love
for s in signal.Signals:
try:
signal.signal(s, self._kill)
except:
pass
python visual-studio-code
I'd like to force sys.exit()
when the python debugger is stopped. When I stop the debugger I see Terminated: 15
so I assume this is SIGTERM
. However, when stopping the debugger, my kill function isn't called.
def kill(sig, frame):
sys.exit(0)
signal.signal(signal.SIGINT, kill)
signal.signal(signal.SIGTERM, kill)
When stopping the vscode debugger, what signal is sent?
Edit:
Just tried all of them. No love
for s in signal.Signals:
try:
signal.signal(s, self._kill)
except:
pass
python visual-studio-code
python visual-studio-code
edited Nov 15 '18 at 18:09
micah
asked Nov 15 '18 at 17:59
micahmicah
3,73712446
3,73712446
SIGHUP
orSIGSEGV
orSIGSTOP
?
– Torxed
Nov 15 '18 at 18:05
@Torxed no luck
– micah
Nov 15 '18 at 18:06
How about this to see if anything triggers? Edited my first comment, I think it'sSIGSTOP
if anything.
– Torxed
Nov 15 '18 at 18:07
Have you added a print statement or something to your kill function, or tried executing it withpython -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).
– Torxed
Nov 15 '18 at 18:25
add a comment |
SIGHUP
orSIGSEGV
orSIGSTOP
?
– Torxed
Nov 15 '18 at 18:05
@Torxed no luck
– micah
Nov 15 '18 at 18:06
How about this to see if anything triggers? Edited my first comment, I think it'sSIGSTOP
if anything.
– Torxed
Nov 15 '18 at 18:07
Have you added a print statement or something to your kill function, or tried executing it withpython -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).
– Torxed
Nov 15 '18 at 18:25
SIGHUP
or SIGSEGV
or SIGSTOP
?– Torxed
Nov 15 '18 at 18:05
SIGHUP
or SIGSEGV
or SIGSTOP
?– Torxed
Nov 15 '18 at 18:05
@Torxed no luck
– micah
Nov 15 '18 at 18:06
@Torxed no luck
– micah
Nov 15 '18 at 18:06
How about this to see if anything triggers? Edited my first comment, I think it's
SIGSTOP
if anything.– Torxed
Nov 15 '18 at 18:07
How about this to see if anything triggers? Edited my first comment, I think it's
SIGSTOP
if anything.– Torxed
Nov 15 '18 at 18:07
Have you added a print statement or something to your kill function, or tried executing it with
python -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).– Torxed
Nov 15 '18 at 18:25
Have you added a print statement or something to your kill function, or tried executing it with
python -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).– Torxed
Nov 15 '18 at 18:25
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325394%2fpython-vs-code-debug-capture-sigterm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325394%2fpython-vs-code-debug-capture-sigterm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
SIGHUP
orSIGSEGV
orSIGSTOP
?– Torxed
Nov 15 '18 at 18:05
@Torxed no luck
– micah
Nov 15 '18 at 18:06
How about this to see if anything triggers? Edited my first comment, I think it's
SIGSTOP
if anything.– Torxed
Nov 15 '18 at 18:07
Have you added a print statement or something to your kill function, or tried executing it with
python -m trace --trace script.py
if that's possible through the debugger you're using? Just to see if any trace of signal handling is occuring? I honestly have no idea what Visual Studio Code is doing and I imagine there's not a lot of documentation on the matter either (seeing as it's pretty new after all).– Torxed
Nov 15 '18 at 18:25