On Mar 18, 2008, at 17:11 PM, Luis Lavena wrote:
> Hello fellow ruby developers!,
>
> Been away a few weeks (work and vacations) and didn't notice until
> today that my CI for several Ruby OSS projects was down. Switching it
> on again showed a few issues with latest Rubygems.
>
> It seems that the changes introduced in trunk (related to tar
> handling) are generating some segmentation faults in Windows:
The changes to tar handling largely involved refactorings, so behavior
should be identical. However, many new tests were added.
> (in D:/Users/Luis/projects/oss/rubygems/rubygems-trunk)
> Loaded suite C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/
> rake_test_loader
> Started
> ...E....E........../lib/rubygems/package/tar_header.rb:211: warning:
> Zlib::GzipWriter object must be closed explicitly.
This appears to be when the GC ran, as the line here is currently:
header.unpack("C*").inject { |a, b| a + b }
and I think that message comes from a Zlib finalizer.
I suspect this has something to do with the previous test errors, as
that message should show up regardless of platform.
> ./lib/rubygems/package/tar_writer.rb:40: [BUG] Segmentation fault
> ruby 1.8.6 (2007-09-24) [i386-mswin32]
And this one is:
@io.write data
I think it will be most-fruitful to look into the test errors first.
I fear that things may not be properly cleaned-up in the tests which
may lead to the segfaults.
> ===
>
> Just wanted to warn about this before an official release/update came
> out. I'll investigate this issue tomorrow afternoon and hope find the
> root of the problem.
>
> I know, Windows... Windows... so much troubles for that damn
> platform :-P
>
> Everybody have a good night :-)
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
