public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ovidr at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18459] [4.0 Regression] gcj no longer works on win32
Date: Sun, 12 Dec 2004 17:40:00 -0000	[thread overview]
Message-ID: <20041212174042.7135.qmail@sourceware.org> (raw)
In-Reply-To: <20041113044458.18459.ovidr@users.sourceforge.net>


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


  parent reply	other threads:[~2004-12-12 17:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13  4:45 [Bug java/18459] New: linux -> win cross compiler : gcj produces corrupt executables ovidr at users dot sourceforge dot net
2004-11-13  5:35 ` [Bug java/18459] " pinskia at gcc dot gnu dot org
2004-11-13 19:22 ` ovidr at users dot sourceforge dot net
2004-11-13 19:56 ` [Bug target/18459] [4.0 Regression] gcj no longer works on win32 pinskia at gcc dot gnu dot org
2004-11-13 20:18 ` dannysmith at users dot sourceforge dot net
2004-11-14 19:35 ` ovidr at users dot sourceforge dot net
2004-11-14 19:38 ` pinskia at gcc dot gnu dot org
2004-11-14 20:25 ` ovidr at users dot sourceforge dot net
2004-11-25 21:40 ` dannysmith at users dot sourceforge dot net
2004-12-10  3:11 ` ovidr at users dot sourceforge dot net
2004-12-10 10:10 ` dannysmith at users dot sourceforge dot net
2004-12-10 16:36 ` ovidr at users dot sourceforge dot net
2004-12-10 23:12 ` dannysmith at users dot sourceforge dot net
2004-12-12 17:40 ` ovidr at users dot sourceforge dot net [this message]
2004-12-12 21:03 ` dannysmith at users dot sourceforge dot net
2004-12-13  0:11 ` ovidr at users dot sourceforge dot net
2004-12-13  8:35 ` cvs-commit at gcc dot gnu dot org
2004-12-13 15:23 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041212174042.7135.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).