KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
My program is determined to stop its execution by hitting CTRL + C in command window. By now, I have a critical error right in this stopping phase, so i want to debug with gdb. Problem is, gdb redefines CTRL + C as its own interrupt and pauses the execution when hitted. How can I handle it that CTRL + C powers my programm off and gdb can catch the stack trace?
Tags (comma-separated)
Save Edits
Cancel