Comment 15 for bug 670571

Mark, no problem, and no apologies required. Fundamentally, the problem is that we do not have a corresponding upstream commit that would fix the bug. In fact, it's not entirely clear whether the bug is fixed upstream or not. Without a good knowledge of the Ruby interpreter code base, it is close to impossible to figure out exactly what is going on.

Also, from what I understand, Dave committed a fix in natty for the specific test-case we currently have (posted by Dan Van Derveer). Does that fix actually address the problem as you experience it? If so, then I guess it could be considered for lucid. If not, then we will need a more specific test-case.

Dave, does the above make any sense to you?