How can I get the RTserver to produce a core file if it fails?
Article ID: KB0092831
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
If the environment variable RT_FATAL_ERROR_ABORT is set to any value (not NULL) then RTserver will abort() immediately and produce a core file instead of asking the user to send SIGQUIT. RTserver should also abort() and produce a core file (as per the output from our signal handler) if a SIGQUIT (usually by typing CTRL-\) is sent within four seconds of a fatal error occurring (i.e. when sent a fatal signal).
NOTE: The system needs to be set up to generate cores when a process aborts (usually this means ulimit -c nonzero; unlimited recommended).
If the environment variable RT_FATAL_ERROR_ABORT is set to any value (not NULL) then RTserver will abort() immediately and produce a core file instead of asking the user to send SIGQUIT. RTserver should also abort() and produce a core file (as per the output from our signal handler) if a SIGQUIT (usually by typing CTRL-\) is sent within four seconds of a fatal error occurring (i.e. when sent a fatal signal).
NOTE: The system needs to be set up to generate cores when a process aborts (usually this means ulimit -c nonzero; unlimited recommended).
Issue/Introduction
How can I get the RTserver to produce a core file if it fails?
Feedback
Yes
No
Powered by
