[#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, NO alloca] Parse.y

From: Michal Rokos <m.rokos@...>
Date: 2002-09-10 09:07:09 UTC
List: ruby-core #475
Hi,

On Tue, Sep 10, 2002 at 07:22:09AM +0900, Yukihiro Matsumoto wrote:
> In message "[Fix, NO alloca] Parse.y"
>     on 02/09/09, Michal Rokos <m.rokos@sh.cvut.cz> writes:
> 
> |	there are some places where we don't need to use alloca.
> |	This is one of these.
> 
> Why do we have to avoid alloca?

	ALLOCA macro just runs alloca. No NULL check is done (and I've
	been said that if alloca fails, not allways returns NULL).

	We run into problems when long we try to alloca big amount of
	memory.

	That's why we should use malloc (where we can).

		Michal

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michal Rokos                         Czech Technical University, Prague
E-mail:m.rokos@sh.cvut.cz      ICQ:36118339      Jabber:majkl@jabber.cz
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

In This Thread