From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | <pgsql(at)mohawksoft(dot)com>, "Nicolai Tufar" <ntufar(at)gmail(dot)com> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-hackers-win32(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: [pgsql-hackers-win32] snprintf causes regression tests to fail |
Date: | 2005-03-01 20:44:56 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE476A1C@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
>> I spent all day debugging it. Still have absolutely
>> no idea what could possibly go wrong. Does
>> anyone have a slightest clue what can it be and
>> why it manifests itself only on win32?
>
>It may be that the CLIB has badly broken support for 64bit
>integers on 32
>bit platforms. Does anyone know of any Cygwin/Ming issues?
>
>Is this only with the new snprintf code in Win32?
Yes.
>Is this a problem with snprintf as implemented in src/port?
Yes. Only. It works with the snprintf() in the runtime (this particular
part).
>Is there a reason why we don't use the snprintf that comes with the
>various C compilers?
It does not support "positional parameters" (I think it's called) which
is required for proper translations.
We do use that one when it works...
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Nicolai Tufar | 2005-03-01 20:57:28 | Re: [pgsql-hackers-win32] snprintf causes regression tests to fail |
Previous Message | pgsql | 2005-03-01 20:38:58 | Re: [pgsql-hackers-win32] snprintf causes regression |
From | Date | Subject | |
---|---|---|---|
Next Message | Nicolai Tufar | 2005-03-01 20:57:28 | Re: [pgsql-hackers-win32] snprintf causes regression tests to fail |
Previous Message | pgsql | 2005-03-01 20:38:58 | Re: [pgsql-hackers-win32] snprintf causes regression |