[#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: nobu.nokada@...
Date: 2002-09-03 15:04:18 UTC
List: ruby-core #414
Hi,

At Tue, 3 Sep 2002 20:35:26 +0900,
Michal Rokos wrote:
> 	I went through ALLOCA_N use and it seems that the ret val of
> 	alloca() is never checked...
> 
> 	Shouldn't we do something like: if (!mem) raise_something()? (I
> 	know that it is a slowdown, but we can catch few segfaults by
> 	this...)

If alloca() were failed, it doesn't always return NULL.

-- 
Nobu Nakada

In This Thread