public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug classpath/20198] java.security.CodeSource.getLocation output is different than expected
Date: Fri, 16 Sep 2005 23:11:00 -0000	[thread overview]
Message-ID: <20050916231052.6292.qmail@sourceware.org> (raw)
In-Reply-To: <20050224180020.20198.bkonrath@redhat.com>


------- Additional Comments From green at redhat dot com  2005-09-16 23:10 -------
(In reply to comment #1)
> Created an attachment (id=9352)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9352&action=view)
> Proposed patch
> 
> This patch makes your test program emit an absolute path.
> 
> I'm not sure it's 100% correct.  For instance, perhaps we should canonicalize
> the path in addition to makeing it absolute.  Also, perhaps this should happen
> in URLClassLoader instead of the system loader.  Hopefully a discussion will
> happen on this thread:
> 
> http://gcc.gnu.org/ml/java-patches/2005-q3/msg00144.html
> 


I just checked in a patch for a related fix.   The test case look like this:

public class bug
{
    public static void main (String args[]) throws Exception
    {
        String urlString =
bug.class.getClassLoader().getResource("bug.class").toExternalForm ();
        System.out.println (urlString);
    }
}

Before patch:

$ gij bug
file:./bug.class

After patch:

$ gij bug
file:/home/green/FSF/HEAD/bug.class

Unfortunately it doesn't fix this bug (although the original patch attached to
this bug _does_).

I'll figure out what else is needed for this bug.

AG


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |green at redhat dot com
                   |dot org                     |
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2005-07-26 22:10:59         |2005-09-16 23:10:50
               date|                            |


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


  parent reply	other threads:[~2005-09-16 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 22:31 [Bug libgcj/20198] New: " bkonrath at redhat dot com
2005-07-24 22:01 ` [Bug libgcj/20198] " green at redhat dot com
2005-07-26 22:11 ` pinskia at gcc dot gnu dot org
2005-07-26 23:29 ` [Bug classpath/20198] " pinskia at gcc dot gnu dot org
2005-09-16 23:11 ` green at redhat dot com [this message]
2005-09-16 23:12 ` cvs-commit at developer dot classpath dot org
     [not found] <bug-20198-10161@http.gcc.gnu.org/bugzilla/>
2006-01-17  1:17 ` tromey at gcc dot gnu dot org
2006-01-17 19:59 ` tromey at gcc dot gnu dot org
2006-01-17 23:25 ` tromey at gcc dot gnu dot org
2006-01-18  0:19 ` tromey at gcc dot gnu dot org
2006-01-18  0:20 ` cvs-commit at developer dot classpath 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=20050916231052.6292.qmail@sourceware.org \
    --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).