public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andreast at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/22253] New: ICE while compiling libjava/gnu/gcj/xlib/natWindow.cc
Date: Thu, 30 Jun 2005 15:16:00 -0000	[thread overview]
Message-ID: <20050630151615.22253.andreast@gcc.gnu.org> (raw)

I get the following ICE:
/Volumes/export/gcc/gcc-cvs/gcc/libjava/gnu/gcj/xlib/natWindow.cc: In member
function 'virtual void gnu::gcj::xlib::Window::setWMProtocols(JArray<jint>*)':
/Volumes/export/gcc/gcc-cvs/gcc/libjava/gnu/gcj/xlib/natWindow.cc:110: internal
compiler error: Bus error

gdb session looks like this:

Starting program: /Volumes/export/gcc/gcc-cvs/objdir/gcc/cc1plus -fpreprocessed
natWindow.ii -feliminate-unused-debug-symbols -fPIC -quiet -dumpbase
natWindow.cc -auxbase-strip gnu/gcj/xlib/.libs/lib_gnu_awt_xlib_la-natWindow.o
-g -O2 -Wswitch-enum -Wextra -Wall -version -fno-rtti -fnon-call-exceptions
-fdollars-in-identifiers -fno-common -o natWindow.s
GNU C++ version 4.1.0 20050630 (experimental) (powerpc-apple-darwin8.1.0)
        compiled by GNU C version 4.1.0 20050630 (experimental).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: de29724eb145ed5e30b8ec939d966d8a

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000030
bitmap_set_bit (head=0x2c, bit=16) at
/Volumes/export/gcc/gcc-cvs/gcc/gcc/bitmap.c:427
427       if (head->current == 0

The config is this one, but I have to try if it fails also with xlib only.

[wolfram:gcc/gcc-cvs/objdir] andreast% ./gcc/xgcc -v
Using built-in specs.
Target: powerpc-apple-darwin8.1.0
Configured with: /Volumes/export/gcc/gcc-cvs/gcc/configure
--prefix=/Volumes/export/gcc/gcc-cvs/testbin --enable-java-awt=gtk,xlib
--enable-gtk-cairo --disable-checking --disable-multilib
--enable-languages=c,c++,java

-- 
           Summary: ICE while compiling libjava/gnu/gcj/xlib/natWindow.cc
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: andreast at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: powerpc-apple-darwin8.1.0
  GCC host triplet: powerpc-apple-darwin8.1.0
GCC target triplet: powerpc-apple-darwin8.1.0


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


             reply	other threads:[~2005-06-30 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 15:16 andreast at gcc dot gnu dot org [this message]
2005-06-30 15:19 ` [Bug middle-end/22253] " andreast at gcc dot gnu dot org
2005-06-30 15:19 ` pinskia at gcc dot gnu dot org
2005-06-30 15:22 ` [Bug middle-end/22253] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-06-30 17:22 ` pinskia at gcc dot gnu dot org
2005-06-30 17:24 ` pinskia at gcc dot gnu dot org
2005-06-30 18:08 ` giovannibajo at libero dot it
2005-07-03 18:23 ` andreast at gcc dot gnu dot org
2005-07-03 18:27 ` pinskia at gcc dot gnu dot org
2005-07-04 15:08 ` andreast at gcc dot gnu dot org
2005-07-04 15:15 ` pinskia at gcc dot gnu dot org
2005-07-14 16:58 ` 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=20050630151615.22253.andreast@gcc.gnu.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).