This is the mail archive of the
mailing list for the Java project.
Re: Natively compiled SWT segfaults under Windows
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: Olivier Parisy <ml dot olivier dot parisy at free dot fr>
- Cc: java at gcc dot gnu dot org
- Date: Tue, 15 Aug 2006 10:03:10 +0530
- Subject: Re: Natively compiled SWT segfaults under Windows
- Openpgp: url=http://ranjitmathew.hostingzero.com/aa_6C114B8F.txt
- References: <44E0933F.firstname.lastname@example.org>
-----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*),
> _Jv_UnwindState*) (
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 can
find the base of the current thread's stack and limit
the values we examine to that address and the current
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://rmathew.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----