Returned the initialize function and just removed the debug code. Without the initialize anything serious crashes the build. Checked it in directly. Roy
Roy Sutton wrote:> Returned the initialize function and just removed the debug code. > Without the initialize anything serious crashes the build. > > Checked it in directly. > > Roy > >Well, that wasn''t it at all, I guess. I had reset my RUBYLIB environment and I was checking the wrong build. The problem is the gem. If I point RUBYLIB at my lib directory the samples run fine. If I use rubygems it crashes. I''m a little stumped right now. I''ll keep poking into it. Roy
Roy Sutton wrote:> Returned the initialize function and just removed the debug code. > Without the initialize anything serious crashes the build.Turns out the problem is garbage collection. With rubygems we''re apparently allocating just enough stuff to get the garbage collector ready to roll on Windows. Without the gems it works fine. I''ll see if I can track the source of this one and maybe fix it. Roy