As I am developing a remote gdb client, I get gdb core dumps from time to time. That wouldn't be so bad, but I also cannot debug gdb with gdb, when the segmentation violation happens, I just get: Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. I tried setting "handle SIGSEGV stop", but that didn't seem to make any difference. Any ideas would be appreciated, Lee _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb
