[#1579] arity bug? — "Christoph" <chr_news@...>
Hi,
5 messages
2003/10/05
[#1588] FreeBSD problem with processes — Laurent Sansonetti <pinux@...>
Hi all,
1 message
2003/10/07
[#1591] Re: Yielding to a block from a proc? — george.marrows@...
> > Is this right? Is this pathological? Is it a bug? Is there
6 messages
2003/10/08
[#1596] PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...>
Hello,
7 messages
2003/10/09
[#1597] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports
— matz@... (Yukihiro Matsumoto)
2003/10/09
Hi,
[#1600] CVS access — Sean Russell <ser@...>
Hiya,
8 messages
2003/10/09
[#1611] set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...>
I've reduced the error I reported in ruby-talk:84013 to the following code:
17 messages
2003/10/11
[#1612] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1616] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1617] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1618] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1634] stringy range bug — "Christoph" <chr_news@...>
Hi,
6 messages
2003/10/15
[#1640] SystemStackError in embedding — Sentinel <sentinel27@...>
Hi, I am just now trying to embed ruby into my apprication
8 messages
2003/10/18
Re: SystemStackError in embedding
From:
Sentinel <sentinel27@...>
Date:
2003-10-19 23:03:59 UTC
List:
ruby-core #1647
> Assuming you're on i686-compatible chips, then this is a known bug that > still has not been fixed, afaik, but I wouldn't know, as I applied the fix > from inside my own program. > > See [ruby-core:01278] (july 2003) in the archives for code on how to find > the real stack-pointer. That was the conclusion to a very frustrating bug > I had been sweating about for a whole year. > > You would then pass the value of that to the following undocumented > function of libruby.so : > > extern "C" void Init_stack(VALUE *addr); > > Matz thinks my solution is not nice: to be exact, when I proposed the > above solution, he said that he didn't know how *he* would do it. > > To avoid the semblance of big hack involving a voluntary segfault and > similar blackmagic, you could hardcode the value 0xBFFFFFFC in your > program, but be warned that this only works on i686-linux and compatible, > and may fail on just about every other platform. > Great many thanks. A quick test with the hardcoded value did the trick. Although I feel a little uneasy about putting your vodoo code into my application (can't see anything wrong with it, still ...) But since I dont have a better idea, and I only need the value at compiletime, I will probably write a mini prog, that generates a header which I can include with the correct stackbase. again many thanks for your help Peter