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 [Summary]


Ranjit Mathew a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

 Olivier Parisy wrote:
> - Compiling with -fno-omit-frame-pointer was not needed. -
> Rebuilding the SWT DLL with the  /Oy- flag was not mandatory.

 I'm not so sure of these two assertions. Perhaps this was not
 necessary in this particular case, but I think it is still needed in
 the general case of trying to unwind through such functions using the
 current fallback_backtrace() function.

Well, as you told me that -fno-omit-frame-pointer was now implicit, the first point seemed logical. But I agree with you on the second one. I just didn't trigger any strange behavior using some basic SWT code, which is fine with me for now.

May any problem happen with stack unwinding in the future, I'll know
I can rebuild the SWT DLL and test again. But considering the
impact on the DLL size, I'll stick to the official one in the mean time.

> In the meantime, could you commit your patch to libjava? As I
> understand it, this should have no side effects, and is needed for
> proper SWT operation.

I've committed the patch to the GCC SVN trunk.

Than you very much.


Best regards,
Olivier Parisy.



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