Dave Thomas <Dave / thomases.com> writes:

> Well, I managed to provoke Ruby into SEGVing with this same code:
> 
> Is this something to do with the latest lazy dup in string.c?

And to followup my own post: if I revert to -r1.23 string.c, the
problem goes away.


Dave