kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

Agreed.  We should have FPE on for debug.  That said, I _think_ they are 
as I just fixed an Eagle import bug that was choking on one.  Of course, 
I might be mistaken and only seen the exception because I was in gdb.

If the code isn't explicit in CMake, we should probably have the "enable 
in debug"/"disable in release" set explicitly.

-Seth

On 2019-05-27 05:12, Jeff Young wrote:
> I think we should at least give it a try.  If we end up getting
> exceptions everywhere then we can either fix them or turn it back off.
>
> Cheers,
> Jeff.
>
>
> > On 27 May 2019, at 09:23, Simon Richter <Simon.Richter@xxxxxxxxxx> 
> > wrote:
> >
> > Hi,
> >
> > I just got a notification that bug #1821758 expired. I'd rather not 
> > ignore
> > this, because I can see that there are likely to be two issues here:
> >
> > - Context code not setting up the floating point environment correctly 
> > on
> >   POWER
> > - Some floating point operation running into an exception (which 
> > itself
> >   shouldn't happen, and usually means that some value is now NaN).
> >
> > I wonder if it would make sense to enable floating point exceptions in
> > Debug builds so we at least stumble over these bugs occasionally.
> >
> > I'd turn the original bug into a "check FPE on POWER" minor bug then.
> >
> >   Simon
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp