If such a program causes a segfault, it's likely to be a bug. But since 5.10.0, there have been 1 major, and 4 minor releases, and a lot of development work for the next major version.

Cut you check whether it still segfaults against 5.12.3 and blead? If it doesn't, the bug has been fixed, and upgrading your perl solves it. If it still isn't fixed, file a bug report, and it may get fixed in 5.14.1 (or if you are really lucky, in 5.14.0).