From: | Larry Rosenman <ler(at)lerctr(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] threads stuff/UnixWare |
Date: | 2004-05-14 01:20:38 |
Message-ID: | 60B7BD71E4C4B7C1975DBC03@lerlaptop.lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
--On Thursday, May 13, 2004 21:14:40 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:
> Larry Rosenman <ler(at)lerctr(dot)org> writes:
>>> Does Unixware support NaN/Infinity at all?
>
>> Yes, we support NaN's and Inf.
>
> Hmph. Apparently their strtod() has thought of some original new way to
> misbehave on those inputs. Would you mind tracing through float4in() or
> float8in() to see exactly how it manages to fail?
>
> regards, tom lane
I ran a quick C test:
cc -O -o test3 test3.c
$ ./test3
num=nan
errno=0
$ cat test3.c
#include <stdlib.h>
#include <stdio.h>
#include <errno.h>
int main(int argc,char **argv)
{
double num;
char *input="NaN";
char **ptr;
num=strtod(input,ptr);
printf("num=%g\n",num);
printf("errno=%ld\n",errno);
exit(0);
}
So, how's the easiest way to trace PG's float4in stuff?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-14 01:26:50 | Re: [HACKERS] threads stuff/UnixWare |
Previous Message | Tom Lane | 2004-05-14 01:14:40 | Re: [HACKERS] threads stuff/UnixWare |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-14 01:26:50 | Re: [HACKERS] threads stuff/UnixWare |
Previous Message | Tom Lane | 2004-05-14 01:14:40 | Re: [HACKERS] threads stuff/UnixWare |