[#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: Allocate crash loop hole.

From: "Christoph" <chr_news@...>
Date: 2002-09-04 00:34:46 UTC
List: ruby-core #424
I wrote

> Hi,
> 
> Ruby's current (admittedly pointless) ability to instantiate
> ``higher order'' meta classes bunches a hole in the new
> defenses around the allocate frame work. The following script
> segfaults on ruby 1.7.3 (2002-08-29) [i386-mswin32]. (Also see
> [ruby-talk: 38612]).  Maybe this is a good enough reason to
> to identify Class and Object.meta(1)?

Never mind .. I run this script with in RDE and picked
a wrong (older) interpreter - the new improved allocate
catches this mistake ...

/Christoph 


In This Thread

Prev Next