On Wed, 27 Mar 2019 06:18:49 -0700, hv wrote: > Now pushed with test as fd8def15a58c97aa89cce8569befded97fd8c3b7. Thanks Sergey for finding this, and to Karl and Hugu for figuring out the fix. I've just hit this SEGV when testing stuff at work with v5.28.1. It's a SEGV at the same location (for the same reason) but despite gdb showing a short regex and a short target string, I wasn't able to get a small testcase out of it (or I think even have it reliably crash), so it's good to see that (1) I don't have to and (2) it's already fixed. My only "problem" now is whether our internal build system is up to installing custom patches, or whether I can sell my boss on v5.30.0 Nicholas Clark --- via perlbug: queue: perl5 status: resolved https://rt.perl.org/Ticket/Display.html?id=133892