On 17 Feb 2008, at 19:19, Marc Santhoff wrote:
That's why I knew I had seen this number, it's in the procedure SignalToRunerror(), so I'm not so stupid after all. ;) Is there any other way of examining the cause besides looking at the values of the variables involved in the calculation?
You could check whether signaltorunerror is maybe missing some entries in its case statement for SIGFPE reasons, and add any missing ones (and if so, submit a patch for that).
Jonas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
