Is this a precompiled mod_jk that you found? If so, then it's simple enough to just grab the latest source for mod_jk and compile it, I suspect this is where your problem is - I've compiled mod_jk against the vendor supplied (Red Hat) Apache a lot of times without segfaults.
Make sure httpd-devel is installed (Red Hat/CentOS)
Unpack the real JDK to some path, like /usr/local/jdk1.6.0_18/
Grab the "tomcat-connectors" source from tomcat.apache.org and compile it:
cd tomcat-connectors-1.2.28-src/native
./configure --with-apxs=/usr/sbin/apxs --with-java=/usr/local/jdk1.6.0_18 --enable-prefork
make
cp apache-2.0/mod_jk.so /etc/httpd/modules/
Your modules should now work as expected.
I think your problem is due to IPV6 that has been turned off, this is quite a common issue, for example read this RedHat report.
If this is the issue you can either turn IPV6 on or submit a bug report to Ubuntu.
If it doesn't help, In general you need a debugger like gdb.
But gdb or any other debugging tool needs debugging symbols of each dependency of the command you need to troubleshoot.
As one link is better than 1000 words, to begin, I advice to read this IBM Developer Works article (a great article honestly).
Be aware that if IPV6 is the issue and you want to solve it yourself, you'll have to download the source code, fix and recompile it
UPDATE
I forgot to mention you can use strace as well to see where ss crash:
strace ss -6
At least you should see the system calls involved.
Best Answer
Such segfaults are usually logged in the system's syslog facility. The exact name of which changes by distro, though
dmesgshould have it if it's recent enough; it'll be in/var/logone way or the other, though.Interpreting the message will be another story entirely. But at least you'll know what faulted.