[patch] fix spurious SIGSEGV faults under Cygwin

Dave Korn dave.korn@artimi.com
Thu Feb 2 17:43:00 GMT 2006

On 02 February 2006 17:38, Daniel Jacobowitz wrote:

> On Thu, Feb 02, 2006 at 05:30:23PM -0000, Dave Korn wrote:
>>   ?????!
>>   I'm having a conceptual difficulty here: Under what circumstances
>> would you expect there *not* to be a debugger attached to the inferior
>> to which the debugger is attached?  That's a bit zen, isn't it?
> You missed that half the patch was for Cygwin - you even sent your reply
> to cygwin-patches. 

  Nope, I didn't miss that bit.  I can see the point in the cygwin side of the patch, for when there _isn't_ a debugger attached,
and the cygwin library has to know whether the exception will be handled by a debugger or whether it has to wrap the access in a

  What I can't see is any point in gdb reading a variable from the inferior that tells gdb if there is a debugger attached to the
inferior, because I can't see how gdb could read that variable except by attaching to the inferior, at which point the value in the
variable should always be 'true', shouldn't it? 

Can't think of a witty .sigline today....

More information about the Cygwin-patches mailing list