public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "zkhan at d2tech dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/35552]  New: GCJ ARM compiled programs give segmentation fault
Date: Wed, 12 Mar 2008 13:25:00 -0000	[thread overview]
Message-ID: <bug-35552-15900@http.gcc.gnu.org/bugzilla/> (raw)

I am trying to run GCJ on ARM9 platform from Texas Instruments / Monta Vista
(MVLCEE3.3.1 OMAP730).

Problem: GCJ builds fine, but when I run programs compiled by it, it gives me
segmentation fault.

This is my target system:
ARM9TDMI
MV Linux 2.4.20
Glibc 2.3.2
Binutils 2.14
GCC 3.3.1


So I cross compiled for this system using crosstool with following parameters:
ARM9TDMI
Linux Headers 2.4.20
Glibc 2.3.2
Binutils 2.14
GCC core 3.4.0
GCC (langs=c,c++,java) 4.2.3

1. arm-9tdmi-linux-gnu-gcc HelloWorld.c -o Hello-c -> Works fine on target
system
2. arm-9tdmi-linux-gnu-c++ HelloWorld.cpp -o Hello-cpp -> Works fine on target
system
3. arm-9tdmi-linux-gnu-gcj HelloWorld.java --main=HelloWorld -o Hello-java ->
Segmentation fault on target (same with -static)


Then I tried another combination of tools to try on QEMU ARM emulator which is
running
ARM9TDMI
Linux 2.6.18
Glibc 2.3.6
Binutils unknown
GCC 4.1.1

Using crosstools made a second set of toolchain
ARM9TDMI
Linux headers 2.6.18
Glibc 2.3.2 (2.3.6 does not build with this combination)
GCC core 3.4.0
Binutils 2.16.1
GCC (langs=c,c++,java) 4.2.3

I have same segmentation fault issue on emulator. I have tried with TLS or
without TLS support, same problem.

Does GCJ work in release 4.2.3?


Some config info from crosstool:
GCC:
/home/zkhan/Desktop/crosstool-0.43/build/arm-9tdmi-linux-gnu/gcc-4.2.3-glibc-2.3.2/gcc-4.2.3/configure
  --target=arm-9tdmi-linux-gnu --host=i686-host_pc-linux-gnu
--prefix=/opt/crosstool/gcc-4.2.3-glibc-2.3.2/arm-9tdmi-linux-gnu
--with-cpu=arm9tdmi --enable-cxx-flags=-mcpu=arm9tdmi
--with-headers=/opt/crosstool/gcc-4.2.3-glibc-2.3.2/arm-9tdmi-linux-gnu/arm-9tdmi-linux-gnu/include
--with-local-prefix=/opt/crosstool/gcc-4.2.3-glibc-2.3.2/arm-9tdmi-linux-gnu/arm-9tdmi-linux-gnu
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit
--enable-shared --enable-c99 --enable-long-long --enable-languages=c,c++,java
--no-create --no-recursion"


-- 
           Summary: GCJ ARM compiled programs give segmentation fault
           Product: gcc
           Version: 4.2.3
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: zkhan at d2tech dot com
 GCC build triplet: -
  GCC host triplet: i686-host_pc-linux
GCC target triplet: arm-9tdmi-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35552


             reply	other threads:[~2008-03-12 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 13:25 zkhan at d2tech dot com [this message]
2008-03-12 16:31 ` [Bug libgcj/35552] " pinskia at gcc dot gnu dot org
2009-06-22 23:25 ` ramana at gcc dot gnu dot org
2009-10-26 20:32 ` dl9pf at gmx dot de
2010-03-20 19:02 ` ramana 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=bug-35552-15900@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).