Replies: 3 comments 3 replies
-
This is more of a LLDB question... I don't think this is possible. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Oh interesting. Thanks.
…On Thu, Aug 5, 2021 at 1:58 PM vadimcn ***@***.***> wrote:
You could try "exitCommands": ["process signal SIGTERM"], though this
seems to work only if the process is not stopped on a breakpoint.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#497 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALTRMO5FZWQKLA7R4JBQSTT3L3QPANCNFSM5BJESA3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Wanted to re-open this since it seems VSCode added an option to the DAP |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm using the CodeLLDB extension to debug an embedded rust application on a raspberry pi.
When terminating my program, I catch the SIGTERM signal and set all the outputs to zero. Otherwise, some pins will carry voltage after shutting down, and this could potentially damage hardware.
When I start a debug session within VSCode and then stop it with the square "stop" button, I think LLDB is sending a SIGKILL signal to my application which causes it to terminate immediately (leaving GPIOs in whatever state they were in right before termination). SIGKILL cannot be caught. Is there a way to configure CodeLLDB or VSCode to send SIGTERM instead?
Beta Was this translation helpful? Give feedback.
All reactions