On 12/4/20 11:44 AM, Corbin Foucart wrote:
Does anyone have any idea
1. Why this exception occurs only at certain refinement levels?
Floating point exceptions happen when you try to do arithmetic on numbers
called "signaling NaNs" that are used as "invalid values" and because the
processor aborts the program when they are used, they're a good way to make
sure that uninitialized values are never used.
Some compilers/operating systems support them, and others don't, so they are
not available on every system. That might explain the difference between the
two systems you are using.
Where the actual exception actually happens in the code is not overly relevant
-- the question is why you give that function uninitialized memory. So in your
case, run the program in a debugger like you're already doing. Look at the
backtrace and go to the last function you were in inside your own program --
then inspect the values of all of the arguments you pass to the function being
called in that place and try to understand why one of these will have these
NaNs in them.
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: [email protected]
www: http://www.math.colostate.edu/~bangerth/
--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see
https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dealii/68b2b035-6c8c-8b2c-a43f-93b0537a4c90%40colostate.edu.
