public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: albert.vdwesthuyzen@fluant.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	tromey@gcc.gnu.org
Subject: Re: java/5028: Possible missing internal function '_Unwind_RaiseException'
Date: Tue, 18 Dec 2001 14:16:00 -0000	[thread overview]
Message-ID: <20011218221626.31848.qmail@sources.redhat.com> (raw)

Synopsis: Possible missing internal function '_Unwind_RaiseException'

Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Tue Dec 18 14:16:26 2001
Responsible-Changed-Why:
    I'm handling this.
State-Changed-From-To: open->analyzed
State-Changed-By: tromey
State-Changed-When: Tue Dec 18 14:16:26 2001
State-Changed-Why:
    Thanks for your report.
    Unfortunately the gcc bug-reporting instructions are a bit wrong for Java.
    The `.i' file you uploaded isn't all that helpful.
    It is just a temporary file that is generated by the compiler.
    
    Is "tibrvsend.java" self-contained?
    If so, could you send it?
    Otherwise, could you send a debugger stack trace?
    
    Thanks.
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5028


             reply	other threads:[~2001-12-18 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 14:16 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-14 23:12 bangerth
2002-05-09 16:53 tromey
2001-12-06  0:16 albert.vdwesthuyzen

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=20011218221626.31848.qmail@sources.redhat.com \
    --to=tromey@gcc.gnu.org \
    --cc=albert.vdwesthuyzen@fluant.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-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).