Signal handling in threads in 2.6 vs. 2.4 kernel

I am debugging multithreaded software on both a 2.4 and 2.6 kernel. Both kernels use LinuxThreads version 0.10. The behavior of the threads/signal handling on the 2.4 kernel is what I would expect...when a thread causes a segfault, the parent process dies with a segfault signal as well. However, on the 2.6 kernel a segfault in a thread causes a SIGKILL in the parent, not a SIGSEGV. This makes it almost impossible to debug multithreaded applications.

I'd appreciate any suggestions anyone might have.

Thanks!
Dustin