Martijn van Oosterhout writes:
> Well, depends how you look at it. The original bug report was about a
> backend crash, which is what happens if you don't catch the SIGFPE. Can
> we guarentee that we know every situation that might generate a SIGFPE?
The point here is that under Windows int4div s
On Wed, Apr 19, 2006 at 10:15:54AM -0400, Tom Lane wrote:
> Martijn van Oosterhout writes:
> > Not that I know of. However, the first step is to add this regression
> > test for SIGFPE [-patches CCed].
>
> This seems completely pointless. The question is not about whether the
> SIGFPE catcher wo
Martijn van Oosterhout writes:
> Not that I know of. However, the first step is to add this regression
> test for SIGFPE [-patches CCed].
This seems completely pointless. The question is not about whether the
SIGFPE catcher works when fired, it's about what conditions trigger it.
[Re: Uncaught exception when dividing integers]
On Tue, Apr 18, 2006 at 10:50:24PM -0400, Bruce Momjian wrote:
>
> Is anyone working on this?
Not that I know of. However, the first step is to add this regression
test for SIGFPE [-patches CCed]. Note that this will probably redline
windows on the
