public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pj at csc dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/12708] SIGSEGV, Segmentation fault starting java program
Date: Wed, 22 Oct 2003 11:36:00 -0000 [thread overview]
Message-ID: <20031022111449.29477.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031021130251.12708.pj@csc.fi>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12708
------- Additional Comments From pj at csc dot fi 2003-10-22 11:14 -------
Subject: Re: SIGSEGV, Segmentation fault starting java
program
On ke, 2003-10-22 at 13:59, bryce at mckinlay dot net dot nz wrote:
> Well, something is very wrong here - looks like a problem with your
> system/glibc headers?
Not very wrong because I can compile 3.3.2 (but it don't work with java)
The compilation problem is only with cvs version.
There can be something wrong, I'll try other computer, which is upgraded
to 9 from RedHat 8.
next prev parent reply other threads:[~2003-10-22 11:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 13:18 [Bug libgcj/12708] New: " pj at csc dot fi
2003-10-21 22:38 ` [Bug libgcj/12708] " bryce at mckinlay dot net dot nz
2003-10-21 22:46 ` bryce at mckinlay dot net dot nz
2003-10-22 7:49 ` pj at csc dot fi
2003-10-22 8:53 ` bryce at mckinlay dot net dot nz
2003-10-22 9:01 ` pj at csc dot fi
2003-10-22 10:49 ` pj at csc dot fi
2003-10-22 11:14 ` bryce at mckinlay dot net dot nz
2003-10-22 11:36 ` pj at csc dot fi [this message]
2003-10-22 12:27 ` pj at csc dot fi
2003-10-22 17:13 ` pinskia at gcc dot gnu dot org
2003-10-22 22:12 ` bryce at mckinlay dot net dot nz
2003-10-23 7:01 ` pj at csc dot fi
2003-12-06 13:57 ` giovannibajo at libero dot it
2003-12-06 13:57 ` giovannibajo at libero dot it
[not found] <bug-12708-4@http.gcc.gnu.org/bugzilla/>
2012-02-07 10:56 ` gyanendra.webmaster at gmail dot com
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=20031022111449.29477.qmail@sources.redhat.com \
--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).