[patch] fix spurious SIGSEGV faults under Cygwin

['Daniel Jacobowitz']

On Thu, Feb 02, 2006 at 05:43:51PM -0000, Dave Korn wrote:
>   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?

He wrote:

> If it turns out that it's expensive, I was thinking that the inferior
> could maintain this information in some variable, and just communicate
> its location to gdb once at startup, then gdb could simply read that
> variable in the process' memory before deciding whether to handle the
> fault.

"this information" does not refer to "if there is a debugger attached".

-- 
Daniel Jacobowitz
CodeSourcery