------- Additional Comments From ovidr at users dot sourceforge dot net 2004-12-12 17:40 ------- I have rebuilt gcc a few times now, after modifying the patch to use #define TARGET_USE_JCR_SECTION 0 and upgrading to a cvs version of binutils.
Using the first patch (http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02192.html) works, and small win32 binaries do run, but when I compile my large app (which uses swt), it still isn't recognized as a win32 app (app.exe is not a valid win32 application) unless I 'strip' it. I don't know how to narrow down the cause of this. (binutils-041211) I then tried out the second patch (dwarf) (http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02120.html) (leaving the first patch still applied), along with Bryce's java stacktrace patch. This worked for me as well on a simple app. On a larger app I still need to strip it, and unfortunately swt uses callbacks, so the app receives a SIGSEGV when closing it: Microsoft Visual C++ Runtime Library --------------------------- Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. (somewhere after _Java_org_eclipse_swt_internal_Callback_unbind -- gdb isn't helpful since the app is stripped). Patch comments (in the dwarf patch) mention a libgcc_s.dll being required in the future? I am hoping that does not mean it would have to be included with every gcj compiled .exe created for wide distribution since it would make apps less self-contained on windows. Anyone have hints on getting around this callback issue? Bryce's stacktrace patch is incredibly helpful with gcj-java compiled apps on win32.. pointers to even a quick and dirty solution would be appreciated. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18459
