The sweep bug is related to something being sweeped and not having a t= ype. Can it=A0be related to this:=A0http://redmine.ruby-lang.org/issues/show/3416=A0?

I've been trying to trace it down but unfortunately I do= n't have Windows 7 running, so I'm lost in the GC's code.

I agree with Evan, this bug is not related with his pat= ch but instead uncovered a bug elsewhere.

---
http://goncalossilva.com

im: goncalossilva@gmail.com
twitter: http://twitter.com/goncalossilva

On Mon, Jul 12, 2010 at 22:07, Evan Phoe= nix <evan@fall= ingsnow.net> wrote:

On Jul 12, 2010, at 1:25 PM, Roger Pack wrote:

>> Roger, could you re-try to build from scratch? =A0Could you apply<= br> >> the test to ruby_1_9_2 and check it is reproducible?
>
> Ok rebuild it from scratch.
> After installing these gems:
> $ gem install redcar rdoc-data win32console rails
>
> then the bug resurfaces.
>
> For the adventurous:
> http://myfavoritepal.com:/incoming/trunk3_installed.7z
> contains the binary that fails.

I don't have access to a windows 7 machine to test this, nor do I= have any knowledge of windows 7 debugging.

I've looked back over your original backtrace. Assuming your still seei= ng the same issue (gc_sweep(), unknown data), I'm guessing that my patc= h is not the core cause of the issue, but is rather just running some code = path that causes a GC bug.

If this is the case, then the GC bug exists already and needs to be fixed w= hether or not my patch is applied.

If this is considered a show stopper for 1.9.2, then it's the GC bug th= at is a show stopper, not my patch. Not applying my patch because of the GC= bug solves nothing, but the GC bug will still exist and users will hit it = some other way.

I currently do not have the knowledge to track down the GC bug, but I hope = that someone on ruby-core does and can assist.

=A0- Evan Phoenix

>
> It's only on one machine though....maybe somebody else with window= s 7
> could try it out and see if it fails? =A0I haven't gotten it to fa= il on
> Linux or XP.
>
> I'll try with 1_9_2 next.
>
> -r
>
>

--0016368334f009bc8c048b384ffb--