From:	fjh AT cs DOT mu DOT oz DOT au (Fergus Henderson)
Subject:	Re: gdb & signals
24 Sep 1997 19:16:27 -0700 :
Message-ID:	<199709250153.LAA25698.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
References:	<19970924132902 DOT 19367 DOT qmail AT hotmail DOT com>
Mime-Version:	1.0
To:	earnie_boyd AT hotmail DOT com (Earnie Boyd)
Cc:	gnu-win32 AT cygnus DOT com (Cygnus GNU-win32 mailing list)

Earnie Boyd wrote:
> 
> >From: Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>
> >
> >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?
> 
> So, which version of cygwin.dll are you using?

I was using b18, although I got the same symptoms with the coolview version.

Anyway I think I've found the cause -- it was the mprotect() in b18.
In b17, there was no mprotect, so my program's configure script noticed
this and didn't try to use it.  In b18, there in an mprotect, but
apparently it doesn't work.

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  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".

- Raw text -