From: | "Larry Rosenman" <ler(at)lerctr(dot)org> |
---|---|
To: | "'Martijn van Oosterhout'" <kleptog(at)svana(dot)org> |
Cc: | "'Michael Fuhr'" <mike(at)fuhr(dot)org>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'PostgreSQL-development'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 2nd try @NetBSD/2.0 Alpha |
Date: | 2005-10-19 14:05:53 |
Message-ID: | 003601c5d4b6$3e5dacb0$0e1993c0@lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
> On Tue, Oct 18, 2005 at 10:07:26PM -0500, Larry Rosenman wrote:
>>> ...or attach with a debugger like gdb.
>>
>> d'oh. I go stupid occasionally :)
>>
>> If someone wants me to, I can try that.
>
> Yes, actually. See, its dying in the seg test already with:
>
> -- Open intervals
> SELECT '0..'::seg AS seg;
> ! ERROR: floating-point exception
> ! DETAIL: An invalid floating-point operation was signaled. This
> probably means an out-of-range result or an invalid operation, s
> uch as division by zero. SELECT '0...'::seg AS seg; ! ERROR:
> floating-point exception ! DETAIL: An invalid floating-point
> operation was signaled. This probably means an out-of-range result or
> an invalid operation, s uch as division by zero.
>
> You need to attach a debugger to find out where that error is
> actually happenening. Just startup the backend, connect to it and
> connect gdb to the newly spawned backend and just run that query by
> hand. Then you should get the backtrace at SIGFPE.
>
I don't have the time today (need to do some paying work). However,
If someone wants, I can pass an ID/PW along so that they
May find it. (or it can wait till the weekend).
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US
From | Date | Subject | |
---|---|---|---|
Next Message | Lyubomir Rusanov | 2005-10-19 14:08:08 | Re: [HACKERS] Call for translators |
Previous Message | Fernando.Figueiredo | 2005-10-19 13:45:28 | Key violation. ERROR: type "lo" does not exist. |