Re: [RFC] sigsetjmp/siglongjmp on cygwin

[Christopher Faylor <cgf at redhat dot com>]

On Mon, Aug 13, 2001 at 04:27:53PM -0700, Keith Seitz wrote:
>On Mon, 13 Aug 2001, Andrew Cagney wrote:
>
>> What about:
>>
>> (gdb) maint internal-error
>> /home/scratch/GDB/src/gdb/maint.c:119: gdb-internal-error: internal
>> maintenance
>> An internal GDB error was detected.  This may make further
>> debugging unreliable.  Continue this debugging session? (y or n) y
>>
>> Create a core file containing the current state of GDB? (y or n) n
>> (gdb)
>
>(gdb) maint internal-error
>/keiths/ref/src/gdb/maint.c:119: gdb-internal-error: internal maintenance
>An internal GDB error was detected.  This may make further
>debugging unreliable.  Continue this debugging session? (y or n) y
>
>Create a core file containing the current state of gdb? (y or n) n
>
>Program received signal SIGSEGV, Segmentation fault.
>0x402acf in return_to_top_level (reason=RETURN_ERROR)
>    at /keiths/ref/src/gdb/top.c:347
>374       (NORETURN void) SIGLONGJMP (*catch_return, (int) reason);
>(top-gdb)
>
>In a previous debugging session (using insight to reproduce this), I
>verified that the contents of catch_return are exactly as sigsetjmp left
>them...

On inspection of cygwin's code, I don't understand how this could be a cygwin
bug.  I've been meaning to investigate this.

I'll do it right now.

In the meantime, I think that configury changes are premature.

cgf