Breaking on Math Warnings?

[Scott Norton <norton(at)optics.rochester.edu>]

Can anyone tell me how to have a program "break" on math warnings in
IDL?
For instance, if Gauss2Dfit doesn't converge, how can I "respond" to
that warning?
Or,
If I get a "% Program caused arithmetic error: Floating underflow", how
do I "check"
for this?
The CATCH procedure explicitely says that it does not "catch" these
types of errors...
"Calling CATCH establishes an error handler for the current procedure
that intercepts all errors that can be handled by IDL, excluding
non-fatal warnings such as math errors."

Thanks!
-Scott
Scott_Norton@surromed.com