<br><br><div class="gmail_quote">On Mon, Apr 7, 2008 at 11:23 AM, Richard Dale <<a href="mailto:richard.j.dale@gmail.com">richard.j.dale@gmail.com</a>> wrote:<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br>Although it made the STACK_LEVEL_MAX figure bigger (15987856 in the above example), it didn't make any difference. I wonder if Ruby is getting the stack direction wrong, I've no idea - so I'll do a bit of googling and investigate further.<br>
</div></div></blockquote><div>Doh! The problem isn't that Ruby is going off the end of the stack, it's that it is dropping below where it believes the stack started. So if I make the stack huge it doesn't have any effect on this underflow. When a ruby plasma plugin is loaded the RUBY_INIT_STACK macro will assume that the stack starts where it happens to be for the plugin loader code. It really needs to be run in main() though as that is where the real root of the stack. One way to work round this is to call RUBY_INIT_STACK at every entry point to the Ruby code (eg virtual method callbacks, and slot invocations). But make sure it is only called once if a virtual method calls another virtual method for instance by incrementing and decrementing a global 'nested_calls' count. Swig uses a couple of macros to do that:<br>
<br>/*<br> If your swig extension is to be run within an embedded ruby and has<br> director callbacks, you should set -DRUBY_EMBEDDED during compilation. <br> This will reset ruby's stack frame on each entry point from the main <br>
program the first time a virtual director function is invoked (in a <br> non-recursive way).<br> If this is not done, you run the risk of Ruby trashing the stack.<br>*/<br><br>#ifdef RUBY_EMBEDDED<br><br># define SWIG_INIT_STACK \<br>
if ( !swig_virtual_calls ) { RUBY_INIT_STACK } \<br> ++swig_virtual_calls;<br># define SWIG_RELEASE_STACK --swig_virtual_calls;<br># define Ruby_DirectorTypeMismatchException(x) \<br> rb_raise( rb_eTypeError, x ); return c_result;<br>
<br> static unsigned int swig_virtual_calls = 0;<br><br>#else /* normal non-embedded extension */<br><br># define SWIG_INIT_STACK<br># define SWIG_RELEASE_STACK<br># define Ruby_DirectorTypeMismatchException(x) \<br>
throw Swig::DirectorTypeMismatchException( x );<br><br>#endif /* RUBY_EMBEDDED *<br><br> Another way might be to provide a longjmp target in the Plasma main() function that the Ruby extension code could jump to and then call RUBY_INIT_STACK there. <br>
<br>Another way would be to always assume that Plasma will load Ruby code, and introduce a link time dependency and just call RUBY_INIT_STACK/ruby_init() in the main(), but I don't think that is very elegant.<br><br>-- Richard<br>
<br></div></div>