From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthias Schmitt <freak002(at)mmp(dot)lu> |
Subject: | Re: OSX doesn't accept identical source/target for strcpy() anymore |
Date: | 2013-10-29 01:48:29 |
Message-ID: | 18561.1383011309@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-10-28 21:14:48 -0400, Tom Lane wrote:
>> They're not all gone according to my testing; but there are far worse
>> problems:
> Spurious or real bugs? Inside PG or libc?
I saw a bunch of uninitialized-value complaints in initdb, apparently from
places in BootstrapXLog that write out uninitialized pad bytes. I didn't
get far in testing the main regression tests because of the autovacuum
crash problem.
> 3. valgrind gets floating point computations for
> exp(larger_negative_double) wrong and returns the wrong error message:
> regression=# SELECT exp(-808.3::float8);
> ERROR: value out of range: overflow
Ugh ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2013-10-29 02:20:02 | Re: OSX doesn't accept identical source/target for strcpy() anymore |
Previous Message | Andres Freund | 2013-10-29 01:29:03 | Re: OSX doesn't accept identical source/target for strcpy() anymore |
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2013-10-29 02:20:02 | Re: OSX doesn't accept identical source/target for strcpy() anymore |
Previous Message | Andres Freund | 2013-10-29 01:29:03 | Re: OSX doesn't accept identical source/target for strcpy() anymore |