[#444] io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...>

I am encountering a problem similar to the one mentioned here,

19 messages 2002/09/06
[#453] Re: io_write()/fwrite() and EINTR on Solaris — nobu.nokada@... 2002/09/08

Hi,

[#454] Re: io_write()/fwrite() and EINTR on Solaris — matz@... (Yukihiro Matsumoto) 2002/09/09

Hi

[#469] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/09

On Mon, Sep 09, 2002 at 03:55:13PM +0900, Yukihiro Matsumoto wrote:

[#479] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/10

On Tue, Sep 10, 2002 at 01:04:10AM +0900, Jos Backus wrote:

[#492] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/21

On Wed, Sep 11, 2002 at 02:23:33AM +0900, Jos Backus wrote:

Re: [Fix] Dir mem leak

From: nobu.nokada@...
Date: 2002-09-11 00:43:28 UTC
List: ruby-core #480
Hi,

At Wed, 11 Sep 2002 01:17:02 +0900,
Yukihiro Matsumoto wrote:
> |I thought 2 approaches, 1) wrap resources by VALUE, 2) use
> |rb_protect() all *func and recursive call, but feel the latter
> |is too complex.
> 
> The latter should not be too complex.  Here's my modifies.  not
> tested.  Maybe it's still incomplete though.

I guessed other functions could raise, i.e. ALLOC_N(), so felt
complex but previous patch got certainly complex too.

-- 
Nobu Nakada

In This Thread