From: | Pete Forman <gsez020(at)kryten(dot)bedford(dot)waii(dot)com> |
---|---|
To: | pgsql-ports(at)postgresql(dot)org |
Subject: | Request for portability test of strerror(). |
Date: | 2000-10-20 11:33:06 |
Message-ID: | 14832.11634.315699.198502@kryten.bedford.waii.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-ports |
I'm preparing a patch for backend/utils/error to make the printing of
error messages more robust. It would be very helpful if people on
different systems would compile and run the following test program to
check the behaviour of strerror().
The PostgreSQL code is called only in exceptional circumstances, so
regular testing of my changes is not possible.
According to the standards UNIX95 (aka XPG4v2) and later, strerror()
should set errno to EINVAL if its argument is out of range. Most
compliant systems seem to return a default string with a number
printed in it and so never set errno.
sys_nerr was last in XPG2 but has now been dropped. I'm hoping to
remove it from the PostgreSQL code.
Attachment | Content-Type | Size |
---|---|---|
strerror.c | text/plain | 501 bytes |
unknown_filename | text/plain | 882 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Pete Forman | 2000-10-20 12:20:42 | Re: Request for portability test of strerror(). |
Previous Message | Jason Tishler | 2000-10-19 13:28:48 | Re: [PATCH]: Building PostgreSQL 7.0.2 on Cygwin 1.1.4 (T ake 2) |