Comment 5 for bug 1915959

The crash is bizarre. I have plenty of other hosts that are making use of mod_perl with no issues at all. It can't be (directly) application specific, as it's crashing before it even gets to running any of the perl. If I uninstall mariadb (required for this application), it starts working again. If I reinstall mariadb, it keeps on working. If I recreate the container from scratch, it reliably starts segfaulting. When I fiddle with it some amount with debug packages and so on, it starts working again and I can't make it break again.

Such is undefined behaviour and invalid memory accesses, I suppose.

You might be able to try debug mod_perl + debug perl - perhaps that will reliably show up the invalid read error in valgrind?

And yes, I did look into submitting the patch upstream but frankly the email system and everything else scared me off. The project doesn't look particularly active either. However, I'll look a bit deeper to see what I can I can do.