This is the mail archive of the
mailing list for the Java project.
Re: Natively compiled SWT segfaults under Windows
- From: Olivier Parisy <ml dot olivier dot parisy at free dot fr>
- To: java at gcc dot gnu dot org
- Cc: Ranjit Mathew <rmathew at gmail dot com>
- Date: Tue, 15 Aug 2006 11:46:36 +0200
- Subject: Re: Natively compiled SWT segfaults under Windows
- References: <44E0933F.firstname.lastname@example.org> <44E14E86.email@example.com>
Ranjit Mathew a écrit :
Should I only compile java code (and the SWT jar) with this flag, or
should the dll be rebuilt with those frame pointers, too?
-----BEGIN PGP SIGNED MESSAGE-----
Olivier Parisy wrote:
I was also able to compile and link basic SWT code, but it dies silently
at run time.
Executing it under GDB, I got:
Program received signal SIGSEGV, Segmentation fault.
fallback_backtrace(_Unwind_Reason_Code (*)(_Unwind_Context*, void*),
The current stack-unwinding code for GCJ/Win32 assumes that
all code is compiled to use frame pointers to link together
call frames on the stack. I suspect that the SWT code has
not been compiled thus (i.e. using -fno-omit-frame-pointer).
Instead of unceremoniously SIGSEGV-ing, perhaps we canConsidering that the current behavior is for the application to die
silently excepted when run in a debugger, that would definitely be an
find the base of the current thread's stack and limit
the values we examine to that address and the current