Re: BLOCK_INPUT on Mac OS X

[Kim F. Storm]

YAMAMOTO Mitsuharu <address@hidden> writes:

> 2. The following library functions are detected as those that may call
>    malloc and so on without BLOCK_INPUT.
> 
>    localtime, gmtime, ctime, opendir, getc, getaddrinfo, fwrite, mkstemp
>    fclose, closedir, freeaddrinfo
> 
>    If the check function in the previous item is correct, should we
>    make a wrapper function for each of them?  Or add BLOCK_INPUTs to
>    caller functions?

Interesting...

If MAC Carbon has problems due to missing BLOCK_INPUT for these
functions, I would imagine that similar problems would be seen on
other systems as well.

Maybe this can explain some of the strange crashes that are (were?)
reported from time to time on some systems?

-- 
Kim F. Storm <address@hidden> http://www.cua.dk