You can handle signals and operating system exceptions in any of the following ways:
When to Simply Debug
To eliminate exceptions that you suspect are due to program logic, use the debugger. For
example, you should correct code that causes a divide by 0 exception, rather than
programming a handler for that condition. The debugger provides complete notification and
stack tracing is available.
Here are some other common problems:
For diagnostic purposes you can build your program with the dump Code Generation option.
![]()
Signals and Exceptions
Signal and Exception Handlers in DLLs
Signals and Exceptions in Critical Functions
Run-Time Library Environments
![]()
Choose Signal or Exception Handlers
Program Signal Handling
Get a Machine-State Dump
![]()
Asynchronous Exceptions
Signals and Default Handlers
Default Exception Handling
(OS/2)
Default Exception
Handling
Exception
Information Provided by OS/2
Prototype of an
OS/2 Exception Handler
OS/2 APIs That
Interfere with Exception Handling
Example of an OS/2 Exception
Handler
Exception Handling for Floating-Point Exceptions
Signal and Exception Handlers in Multithreaded Programs
Critical Functions
Floating-Point Bit Masks
Signal and Exception Handling Considerations
