public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jianlin Chang <chang@platform.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: RE: java/3307: compiled program core dump in GC_find_limit
Date: Mon, 09 Jul 2001 15:56:00 -0000 [thread overview]
Message-ID: <20010709225602.26130.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR java/3307; it has been noted by GNATS.
From: Jianlin Chang <chang@platform.com>
To: "'Andrew Haley'" <aph@cambridge.redhat.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: RE: java/3307: compiled program core dump in GC_find_limit
Date: Mon, 9 Jul 2001 18:55:13 -0400
>-----Original Message-----
>From: Andrew Haley [ mailto:aph@cambridge.redhat.com ]
>Sent: Monday, July 02, 2001 2:56 PM
>To: chang@platform.com
>Cc: gcc-gnats@gcc.gnu.org
>Subject: Re: java/3307: compiled program core dump in GC_find_limit
>
>
>Thanks for the report.
>
>Firstly, Solaris support for gcj is not totally complete in 3.0.
>
>Secondly, I can't fix this problem as I don't have the source that I
>need. However, it does look as though there is a problem with the
>interface between the exception handler library and libgcj.
>
>One thing that you could try before we go any further: do trivial
>catch/throw examples work for you?
Yes, it does.
next reply other threads:[~2001-07-09 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 15:56 Jianlin Chang [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 16:44 rodrigc
2001-12-18 9:40 tromey
2001-07-14 8:05 green
2001-07-02 12:06 Andrew Haley
2001-06-21 9:46 Jianlin Chang
2001-06-21 9:26 Tom Tromey
2001-06-20 14:46 chang
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=20010709225602.26130.qmail@sourceware.cygnus.com \
--to=chang@platform.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).