On Sun Feb 15 17:39:17 2015, sprout wrote: > I have finally fixed this in e47d32d. What I said about skipspace was > not correct. skipspace was doing the right thing, but many other > paths were calling lex_read_space or lex_next_chunk without the proper > guards. But putting guards all over the place seemed the wrong > approach, so I modified lex_next_chunk instead. I followed up with another fix in d27f4b9. A similar case was still crashing. -- Father Chrysostomos --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=123712Thread Next