This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Debugging libgcj on cygwin

Jeff Sturm wrote:
On Tue, 1 Jul 2003, Thomas Pfaff wrote:

If so, backporting Andrew's patch to 3.3 is one solution.


Yup, this fixes it if as long as i configure with --disable-interpreter.

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:

Program received signal SIGSEGV, Segmentation fault.
_Jv_InterpMethod::run(void*, ffi_raw*) (this=0x1014be60, retp=0x22f730, args=0x22f750) at ../../../gcc-3.3/libjava/include/java-interp.h:230
230 next = *n;

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.

Thomas

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]