Dear Dan,
I tried your code using Ruby 1.8.4, Windows XP, Cygwin.
I do not get a segmentation fault there.
So it doesn't appear to have to do with Ruby.
Recently, there were quite some people posting about
segfault problems when running applications on Windows -
ruby-gsl, fxruby, and now win32api.
Does anybody know anything why Windows behaves that way?
Best regards,
Axel
Nuralanur@aol.com wrote:
Dear Dan,
I tried your code using Ruby 1.8.4, Windows XP, Cygwin.
I do not get a segmentation fault there.
So it doesn't appear to have to do with Ruby.
Recently, there were quite some people posting about
segfault problems when running applications on Windows -
ruby-gsl, fxruby, and now win32api.
Does anybody know anything why Windows behaves that way?
Best regards,
Axel
I don't think the bug I posted (which now appears to be sporadic, btw) is necessarily related to the bugs reported in ruby-gsl or fxruby.
It could be a bug in string.c. Or, it could be a compiler bug. Or, it could be some issue with regards to Windows IO stream, since a 'puts' will sometimes mysteriously solve (or cause) a segfault.
Regards,
Dan