This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Debugging libgcj on cygwin
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Thomas Pfaff <tpfaff at gmx dot net>
- Cc: java at gcc dot gnu dot org
- Date: Fri, 11 Jul 2003 00:26:18 -0400 (EDT)
- Subject: Re: Debugging libgcj on cygwin
On Mon, 7 Jul 2003, Thomas Pfaff wrote:
> > What happens with the interpreter?
>
> The interpreter seems to be broken on cygwin, therefore i configure with
> --disable-interpreter. If i configure with --enable-interpreter the
> result is the same as without the patch:
I see. BTW I applied a simpler patch to 3.3 that ought to solve your
problem. (3.3.1 will be closed starting tomorrow and should be released
soon.)
> I think that the main problem with cygwin is that signals (especially
> SIGSEGV) are not thread safe at the moment. SIGSEGV is only handled
> correctly by the main thread.
As Tom Tromey said, cygwin should build with -fcheck-references so signal
handling is unneeded.
My real concern is that boehm-gc doesn't seem to handle posix threads for
cygwin. However a plain no-threads build should test OK in libjava.
BTW I tried a full bootstrap & check running cygwin on a win2k box; do you
know how to avoid the popup dialogs for each faild executable? It makes
it difficult to run an automated testsuite.
Jeff