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: Natively compiled SWT segfaults under Windows


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
top-of-stack.

HTH,
Ranjit.

- --
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

iD8DBQFE4U6GYb1hx2wRS48RAkioAJsGduky4Pcj8Ih7ywBNIguPy9c5rACcC93j
0erzQlv5COvDsCOI/EaHODM=
=xvy4
-----END PGP SIGNATURE-----


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