I read here recently that because of the way Linux formats its core dump files, you only get one thread of a multithreaded program when using gdb on the core dump file. Can anyone suggest a way of tracking down where a segmentation fault is happening in a multithreaded program? We're catching the SIGSEGV signal with sigaction but that doesn't give us very much information or we don't know how to use that information properly. Any help is greatly appreciated. Thanks Keith Clifford _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb