public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "hannes at helma dot at" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/16481] New: Wrong stack trace in conjunction with custom ClassLoaders
Date: Sun, 11 Jul 2004 23:19:00 -0000	[thread overview]
Message-ID: <20040711231909.16481.hannes@helma.at> (raw)

There is a problem with stack traces in conjunction with user defined
URLClassLoaders. The frames from classes loaded via that ClassLoader are missing
from the stack. This seems to happen regardless of wheather the code loading the
classes is compiled or interpreted. 

One impact of this is that loaded ClassLoader fail to get a
java.util.ResourceBundle. I'm uploading a test case for this.

I encountered this on gcj 3.3.3, but it is still present in the 3.5.0 20040704
snapshot.

-- 
           Summary: Wrong stack trace in conjunction with custom
                    ClassLoaders
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hannes at helma dot at
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16481


             reply	other threads:[~2004-07-11 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-11 23:19 hannes at helma dot at [this message]
2004-07-11 23:21 ` [Bug libgcj/16481] " hannes at helma dot at
2004-07-14 20:41 ` mckinlay at redhat dot com
2004-10-21 13:22 ` aph at gcc dot gnu dot 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=20040711231909.16481.hannes@helma.at \
    --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).