How to programmatically break into gdb from gcc C++ source
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is a way to attach the debugger process explicitly (I've seen it done but have no idea how to do it).
If you're starting from the debugger, then you can signal() your own process with SIGINT to interrupt it and return control to the debugger, effectively a breakpoint. That won't work very well if you're doing signal-handling though. See the signal manpage for more.
gdb mycode
gdb> run
Program received signal SIGINT, Interrupt.
0x705b28a0 in kill () from /usr/lib/libc.2
... you are now in the debugger right after the BREAK_HERE statement
You will have to step twice to come back out of the raise() call into your code.
Just a note on this. I'm using ddd, and I find that after the SIGINT, I have to use 'stepi' 4 times (ie step 4 instructions), and then 'step' once (i.e step to next source line). This gets ddd synchronised with the source line.
Otherwise I get "Cannot find bounds of current function" errors in ddd.
Would be nice if there was a way to get ddd to go straight to the offending source line on the SIGINT, but I can live with this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.