Home/ Questions/Q 6079991
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T11:00:39+00:00

I’m developing an application (a service/daemon, really) on Linux in C++ that needs to

  • 0

I’m developing an application (a service/daemon, really) on Linux in C++ that needs to interface with a piece of hardware. If my program doesn’t release the resources for this peice of hardware cleanly when terminating, then I have to reload the device driver, a process that takes about 10 minutes and for obvious reasons having to wait 10 minutes between each test of the program would be frustrating.

So I have used the sigaction() function to catch a SIGINT (a ctrl-c) so that my program can cleanly shutdown when I’m finished with it. When running the program from the console, this works fine. However, when debugging in Netbeans or Eclipse (I’ve tried both) things don’t work.

  • In Eclipse, if I hit ctrl-c in the console it provides, it doesn’t seem to register that a SIGINT ever occurred
  • In Eclipse, if I run the program in debug mode and then use kill -SIGINT <pid>, the program just breaks as if it hit a breakpoint
  • Netbeans actually seems to realise a signal has been sent when I hit ctrl-c in the console, and pops up a dialog asking if I want to forward it to the application. Clicking “Forward and continue” just seems to break the program and the signal is not received by the application. It also says I can configure this stuff in Debug -> Dbx configure, a menu item that doesn’t exist
  • In Netbeans, if I run the program in debug mode and then use kill -SIGINT <pid>, the behaviour is the same as above
  • I then added a SIGQUIT handler and tried sending that via kill when debugging in Netbeans. This time, no dialog appears and the signal handler is never tripped.

I need some way to cleanly shutdown my app while I’m debugging. Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It turns out the problem had nothing to do with Netbeans or Eclipse, but rather gdb.

    gdb can be configured to handle signals in a variety of ways. If you run:

    gdb

    then type:

    info signals

    You’ll get a list of signals and gdb actions on what to do if it receives that signal:

    Signal        Stop      Print   Pass to program  Description

SIGHUP        Yes       Yes     Yes              Hangup
SIGINT        Yes       Yes     No               Interrupt
SIGQUIT       Yes       Yes     Yes              Quit
SIGILL        Yes       Yes     Yes              Illegal instruction
SIGTRAP       Yes       Yes     No               Trace/breakpoint trap

    etc…

    My temporary work around has been to use SIGALRM which gdb defaults to not breaking and sending to the process. However, you can also customise the default gdb settings by creating a .gdbinit file where you can set these

    • 0