Terminate program hitting CTRl+C within GDB

本文介绍了在使用GDB调试程序时如何正确处理CTRL+C操作,以实现程序正常中断并获取堆栈跟踪信息。文中提供了两种方法:一是通过输入'signal SIGINT'指令发送信号给被调试程序;二是配置GDB使SIGINT信号直接传递给被调试进程。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Q:

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 whet hitted. How can i handle it that CTRL+C powers my programm off and gdb can catch the stack trace?

A:

rom the (gdb) prompt, type signal SIGINT. This will send (surprize) SIGINT to the program being debugged.

Alternatively, handle SIGINT nostop print pass will make GDB pass the signal straight to the inferior (being debugged) process.

转载于:https://www.cnblogs.com/androidme/p/3504846.html

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值