# Note: The following floating-point exceptions are signalling: IEEE\_INVALID\_FLAG IEEE\_DIVIDE\_BY\_ZERO

**URL:** <https://fortran-lang.discourse.group/t/note-the-following-floating-point-exceptions-are-signalling-ieee-invalid-flag-ieee-divide-by-zero/5470>\
**Category:** Uncategorized\
**Created:** [March 30, 2023, 5:50pm UTC](https://fortran-lang.discourse.group/t/note-the-following-floating-point-exceptions-are-signalling-ieee-invalid-flag-ieee-divide-by-zero/5470 "2023-03-30T17:50:42Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![FortranFan](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@FortranFan](https://fortran-lang.discourse.group/u/FortranFan)\
**Post date:** [March 30, 2023, 8:25pm UTC](https://fortran-lang.discourse.group/t/note-the-following-floating-point-exceptions-are-signalling-ieee-invalid-flag-ieee-divide-by-zero/5470/8 "2023-03-30T20:25:10Z")

</div>

> [@lmiq](#):
>
> … Does anyone has any tip on how to debug that, given that the program does not throw any error? …

@lmiq,

Please take a look at the trivial example in this [**thread**](https://fortran-lang.discourse.group/t/exceptions-proposal/5160/10) as just an illustration. The point being whether it is possible for you to consider standard Fortran IEEE-related intrinsics toward `SET_HALTING_MODE`, `IEEE_SET_FLAG`/`IEEE_GET_FLAG`, etc… A judicious use of these intrinscis can enable you to trap the floating-point exceptions or even break at the right location(s) that may be deep inside some number-crunching library(ies).

---

_[View the full topic](https://fortran-lang.discourse.group/t/note-the-following-floating-point-exceptions-are-signalling-ieee-invalid-flag-ieee-divide-by-zero/5470)._