Re: FreeBSD bugs

[Ed Maste]

On 2 October 2012 10:30, Ed Maste <address@hidden> wrote:

> Thanks for the list - here's the current status, on 9.1 prerelease.
> It'll take a little while to fully analyze the remaining failures.

Here are some additional details and a re-sorted list.

*** Already fixed or in progress:

>> fcntl
>> This function does not support @code{F_DUPFD_CLOEXEC} on some
>> platforms:

Actually, already fixed.
http://www.freebsd.org/cgi/query-pr.cgi?pr=169962
http://svnweb.freebsd.org/base?view=revision&amp;revision=238834

>> getgroups
>> On some platforms, this function fails to reject a negative count,
>> even though that is less than the size that would be returned:

PR standards/172276
http://www.freebsd.org/cgi/query-pr.cgi?pr=172276

>> unsetenv
>> On some platforms, this function does not fail with @samp{EINVAL} when
>> passed an empty string or a string containing @samp{=}:

PR standards/172273
http://www.freebsd.org/cgi/query-pr.cgi?pr=172273

*** More investigation of the autoconf tests needed:

>> link
>> This function fails to reject trailing slashes on non-directories on
>> some platforms:
>
> I didn't find the specific test for this one.
>
>> remove
>> This function fails to reject trailing slashes on non-directories on
>> some platforms:
>
> I see REPLACE_REMOVE='1', but don't see a test corresponding to this.

*** Remaining issues:

>> fclose
>> On some platforms, this function fails to set the file position of a
>> seekable input stream to the byte after the last one actually read:
>
>> fflush
>> @code{fflush} on an input stream right after @code{ungetc} does not discard
>> the @code{ungetc} buffer, on some platforms:
>
> configure:21795: checking whether fflush works on input streams
> configure: program exited with status 4
>
>> fdopendir
>> This function mistakenly closes non-directory file descriptors on some
>> platforms:
>
>> *printf
>> This function can crash in out-of-memory conditions on some platforms:
>
> configure:17513: checking whether printf survives out-of-memory conditions
> configure:17735: result: no
>
>> modf
>> This function has problems with infinite arguments on some platforms:
>
> configure:70726: checking whether modf works according to ISO C 99
> with IEC 60559
> configure: program exited with status 2
>
>> pthread_sigmask
>> This function does nothing and always returns 0 in programs that are not
>> linked with @code{-lpthread} on some platforms:
>
> configure:76179: checking whether pthread_sigmask works without -lpthread
> configure:76219: result: no
>
>> strstr
>> This function has quadratic instead of linear worst-case complexity on some
>> platforms:
>
> configure:89105: checking whether strstr works in linear time
> configure:89190: result: no