Comment # 3 on bug 1089916 from James Oakley

If you want to get more information on the segfault, you can install the
debuginfo packages for every library you see in the traceback, and use gdb to
inspect the stack.

If you are using any sort of threading, I would also recommend checking to see
if you can reproduce without threading, since these things can be caused by the
use of threading with libraries that are not thread-safe.

If you are using autoload, then it tries to figure out what modules to load
based on the other statements in the config, so something else in the config is
probably triggering that. Perhaps a module that is not installed. I would
recommend not using autoload and specifying modules explicitly. (Explicit is
better than implicit, after all)