[#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: Should we check alloca ret val?

From: ts <decoux@...>
Date: 2002-09-03 16:02:01 UTC
List: ruby-core #417
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:

n> I read it and posted [ruby-core:00414].  In this case, I guess
n> the best way would be to get rid of alloca(), but it may not be
n> desirable and even possible always.

 and if someone use a *very big* regexp ? r_bytes2() is also used for
 a regexp 


Guy Decoux

In This Thread