This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] sigsetjmp/siglongjmp on cygwin
- To: Keith Seitz <keiths at cygnus dot com>
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Mon, 13 Aug 2001 18:51:56 -0400
- Cc: Jim Blandy <jimb at cygnus dot com>, gdb-patches at sources dot redhat dot com
- References: <Pine.GSO.4.33.0108131540260.22492-100000@makita.cygnus.com>
> Yes, I think that is what every one is stumped on. Making it more
>> difficult, a compile time rather than a runtime test is probably needed
>> - otherwize it won't be possible to canadian cross GDB.
>>
>> Perhaphs the real problem is GDB corrupting its stack? Can you explain
>> the test case or is it just ``normal use''?
>
>
> It's easy to reproduce once you have gdb built with sigsetjmp/siglongjmp.
> Just boot Win98 and run gdb. Do something, ANYTHING to call
> return_to_top_level. I did "info func" on gdb. When the pager was done
> outputting the first page of functions, I asked it to "quit" instead of
> continuing the listing. Boom! It died immediately.
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)
Andrew