public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/47456] internal compiler error: Segmentation fault while using jna
Date: Wed, 26 Jan 2011 00:20:00 -0000 [thread overview]
Message-ID: <bug-47456-8172-aG54JuMK3W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47456-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47456
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011.01.26 00:20:46
Ever Confirmed|0 |1
Severity|blocker |normal
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-01-26 00:20:46 UTC ---
Can you provide the exact output of "gcc -v"? And also attach the jar file
which you are trying to compile with the exact command line?
next prev parent reply other threads:[~2011-01-26 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 11:20 [Bug java/47456] New: " steve.reinke at iws dot fraunhofer.de
2011-01-25 11:21 ` [Bug java/47456] " steve.reinke at iws dot fraunhofer.de
2011-01-26 0:20 ` pinskia at gcc dot gnu.org [this message]
2011-01-26 6:32 ` steve.reinke at iws dot fraunhofer.de
2011-01-26 6:57 ` steve.reinke at iws dot fraunhofer.de
2011-01-27 11:31 ` steve.reinke at iws dot fraunhofer.de
2011-01-27 12:05 ` mikpe at it dot uu.se
2011-02-01 7:52 ` steve.reinke at iws dot fraunhofer.de
2011-02-01 9:40 ` mikpe at it dot uu.se
2011-02-01 13:14 ` steve.reinke at iws dot fraunhofer.de
2011-02-01 14:12 ` mikpe at it dot uu.se
2011-12-13 9:14 ` ktietz at gcc dot gnu.org
2012-01-10 16:58 ` ktietz at gcc dot gnu.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-47456-8172-aG54JuMK3W@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).