From: fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson) Subject: gdb & signals 23 Sep 1997 12:10:50 -0700 Message-ID: <199709231841.EAA24080.cygnus.gnu-win32@mundook.cs.mu.OZ.AU> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: gnu-win32 AT cygnus DOT com Hi, My program, which I think works OK with b17.1, gets a seg fault or equivalent ("In cygwin_except_handler") with b18. On win95, it hangs the OS. On NT it is not quite so bad, I can kill the process. But I'm having trouble debugging it, because after the first SIGSEGV -- which is expected (my program is trapping the signal) -- gdb refuses to continue, complaining that it can't send the signal to the child process. So I can't reproduce the problem inside gdb. Also the gdb `attach' command doesn't seen to work either, so I can't attach to the process after it has hung. Any hints or suggestions for how to go about debugging this sort of problem? -- Fergus Henderson | "I have always known that the pursuit WWW: | of excellence is a lethal habit" PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3 | -- the last words of T. S. Garp. - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".