"Lyle Johnson" <ljohnson / resgen.com> writes:

> > Has anyone come across strange segv's and the like in Ruby apps
> > under Windows 2000?
> >
> > We have a Ruby application that runs absolutely fine under Linux,
> > Windows 98, and Windows NT. Under 2000, however, it will eventually
> > and repeatably corrupt things and blow up. The current symptom we're
> > seeing is that flo_to_s in numeric.c seems to corrupt the stack doing
> > a sprintf.
> 
> As a good friend of mine likes to say, "the absence of a
> manifestation of a bug does not equal the absence of a bug." ;)
> Based on Ben Tilly's response you might want to see if you can get
> your hands on a good memory-problem-debugger like Purify. I no
> longer have access to any such tools at my current employer (where
> we're a mostly-Java shop), otherwise I'd volunteer for the task.

Unfortunately we've run this under Bounds Checker and it passes with
no problems. We've also run it using a debugging MALLOC with no
reported problems.

We've also discovered that the problem changes character depending on
the level of compiler optimization chosen (although we're not
convinced it's a code generation problem).

I'm beginning to suspect an uninitialized pointer in the interpreter, but 
it's proving to be a bear to track down.


Thanks


Dave