I have an application where some component occasionally inserts a qNaN in a large data stream, which then invalidates the entire processing (FFT on a vector containing a single qNaN results in an all-qNaN output). Now I'd like to catch that component in the act and find out why it's doing that.
For this, I'd need to somehow make all NaNs signalling during debug. Is there a way to do so, with a x64 CPU executing 32 bit code?
If you want to make all NaNs, overflows, and zerodivides signaling during debug, it is possible.
For gcc:
#include <fenv.h>
#ifndef NDEBUG
feenableexcept(FE_DIVBYZERO | FE_INVALID | FE_OVERFLOW);
#endif
For Visual Studio (not tested):
#include <float.h>
#ifndef NDEBUG
_clearfp();
_controlfp(_controlfp(0, 0) & ~(_EM_INVALID | _EM_ZERODIVIDE | _EM_OVERFLOW),
_MCW_EM);
#endif
References: Microsoft, gcc.
These functions allow to catch either NaNs, produced by floating point operations (overflows, zerodivides, invalid operations), or sNaNs, used as input to some floating point operation. They do not allow to catch qNaNs, used as input to floating point operation. For such qNaNs, the only way to find them is to check each value individually (see Luchian Grigore's answer).
So if the component, that inserts a qNaN is in the same program, were you want to catch it, or if this component is in separate program, but you have its source codes, just enable FP exceptions with feenableexcept()
/_controlfp()
. Otherwise, check every value in the incoming data stream with isnan()
(C++11) or with x != x
.
I doubt there's a way to put a data breakpoint all over the memory to catch all NaNs
.
I'd look for the code that inserts into the vector
and test for NaN
there:
if ( x != x )
assert(!"NaN detected");
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With