PM82904: SIGSEGV not caught by signalhandler when using fprintf
Closed as unreproducible in next release.
We have a software that uses the Rhapsody OXF framework with the Cygwin Environment on Windows. The Application uses multithreading and does extensive logging to a file with fprintf() (from a single thread). In case of a software failure we would like to write the buffered log information to the file, close it properly and do some hardware settings. For this reason we have implemented our own signalhandler which is registered with the system via the sigaction() call. Everything seems to work fine, except that crashes in certain areas of the software are sometimes not caught by the handler. To find the cause, we set up a test project, first in Rhapsody and later in Eclipse. We found out that we're having trouble capturing hardware exceptions/signals when fprintf() is used in certain areas of the software. In this case the signalhandler is not called and the software crashes immediately. Using streams seems to work but could not be tested extensively. Within a plain Eclipse project (no Rhapsody framework) everything works fine, so the assumption is that it has something to do with the framework.
SIGSEGV not caught by signalhandler when using fprintf
This defect is not reproducible.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
More support for:
Software version: 7.6.1
Reference #: PM82904
Modified date: 12 December 2013
Translate this page: