[#1207] warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...>

This message was posted to ruby-talk, but I didn't get responce from

22 messages 2003/07/01
[#1208] Re: warning in ruby extension eats memory — ts <decoux@...> 2003/07/01

>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:

[#1209] Re: warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...> 2003/07/02

ts wrote:

[#1210] Re: warning in ruby extension eats memory — ts <decoux@...> 2003/07/02

>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:

[#1211] Re: warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...> 2003/07/04

ts wrote:

[#1212] Re: warning in ruby extension eats memory — ts <decoux@...> 2003/07/04

>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:

[#1213] Re: warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...> 2003/07/04

ts wrote:

[#1214] Re: warning in ruby extension eats memory — ts <decoux@...> 2003/07/04

>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:

[#1215] Re: warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...> 2003/07/04

ts wrote:

[#1237] FTP.new with block — Gavin Sinclair <gsinclair@...>

Hi,

22 messages 2003/07/19
[#1238] Re: [Patch] FTP.new with block — ts <decoux@...> 2003/07/19

>>>>> "G" == Gavin Sinclair <gsinclair@soyabean.com.au> writes:

[#1240] Re: [Patch] FTP.new with block — Mathieu Bouchard <matju@...> 2003/07/19

[#1297] Fix for Bug 1058 — Markus Walser <walser@...>

Hi,

16 messages 2003/07/25

Re: stack problem

From: Mathieu Bouchard <matju@...>
Date: 2003-07-14 16:26:43 UTC
List: ruby-core #1233
On Sun, 13 Jul 2003, Mathieu Bouchard wrote:

> 
> On Sat, 12 Jul 2003, Mauricio Fern疣dez wrote:
> > You can use Init_stack, see the thread starting at [ruby-talk:74400].
> Thanks. If I understood correctly, I have to use it like this?

As an explanation for the code snippet: I want to find the bottom of the
stack, to tell Init_stack about it, because it can't find it by itself; i
could use (VALUE *)0xBFFFFFFC, but I want to be a bit more
system-independant than that... Is there a quicker, systematic way of
finding the bottom of the stack?

My problem is that ruby_init() doesn't run from the main(), and cannot be
made to, because I embed Ruby inside a plugin (.so) for another
program. So my program has no main() by itself, and may be initialized as
any number of things are on the stack. That number of things used to
influence the frequency of crashes I would get (!!!).

Over the last months I had come to equating Ruby with unreliability
because I didn't know that Ruby couldn't figure out the bottom of the
stack. Now it's much better but the fix looks quite a bit weird.

________________________________________________________________
Mathieu Bouchard                       http://artengine.ca/matju



In This Thread