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: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: Keith Seitz <keiths at cygnus dot com>
- Date: Mon, 13 Aug 2001 15:43:40 -0700 (PDT)
- cc: Jim Blandy <jimb at cygnus dot com>, <gdb-patches at sources dot redhat dot com>
On Mon, 13 Aug 2001, Andrew Cagney wrote:
> > Would love to do this, but, unfortunately, writing a simple test to do
> > this is not so easy. The problem is that sigsetjmp/siglongjmp are, for
> > lack of a better phrase, "flakey". Ever simple testcase I come up with
> > works just fine, but I can get gdb to crash instantly...
>
>
> 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.
Of course, the bigger problem for me is that Insight causes gdb to call
return_to_top_level all the darn time, so Insight crashes immediately. :-(
Keith