public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: andreas.lenz@handy-games.com
To: gcc-gnats@gcc.gnu.org
Subject: java/6319: gcj segfault on empty .java file
Date: Tue, 16 Apr 2002 03:56:00 -0000 [thread overview]
Message-ID: <200204161048.g3GAmEf30547@Twisty.local> (raw)
>Number: 6319
>Category: java
>Synopsis: compiling an empty .java file failes
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Tue Apr 16 03:56:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:
>Release: 3.0.4
>Organization:
>Environment:
System: Linux Twisty 2.4.0 #5 Mit Mai 30 16:05:26 CEST 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ./configure
>Description:
I use the c preprocessor on .java code and some .java files only have some empty lines if DEBUG is 0
Compiling these files causes gcj to segfaulti.
It's no big thing, I even don't know, if empty .java files are allowed, but gcj suggests to
fill out a bug report...
Greets
Andi
>How-To-Repeat:
>Fix:
I have
#else
public class debug_report {}
#endif
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-04-16 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200204161048.g3GAmEf30547@Twisty.local \
--to=andreas.lenz@handy-games.com \
--cc=gcc-gnats@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).