Unthreaded applications

 

(Not applicable on Solaris as all applications are considered threaded even if they use only a single thread.)

Each MQI function sets up its own signal handler for the signals:

Users' handlers for these are replaced for the duration of the MQI function call. Other signals can be caught in the normal way by user-written handlers. If you do not install a handler, the default actions (for example, ignore, core dump, or exit) are left in place.

After WebSphere MQ handles a synchronous signal (SIGSEGV, SIGBUS, SIGFPE, SIGILL), it attempts to pass the signal to any registered signal handler before making the MQI function call.

 

Parent topic:

UNIX signal handling


fg11920_