From: Stephen Crawley <crawley@dstc.edu.au>
To: Brian Jones <cbj@gnu.org>
Cc: Stephen Crawley <crawley@dstc.edu.au>,
classpath@gnu.org, "Raif S. Naffah" <raif@fl.net.au>,
Mauve <mauve-discuss@sources.redhat.com>
Subject: Re: classpath ./ChangeLog ./THANKYOU ./configure.in...
Date: Mon, 07 Apr 2003 16:09:00 -0000 [thread overview]
Message-ID: <200304071608.h37G8siE021877@piglet.dstc.edu.au> (raw)
In-Reply-To: Message from Brian Jones <cbj@gnu.org> of "06 Apr 2003 23:33:56 -0400." <m3istrt1zv.fsf@lyta.haphazard.org>
> Stephen Crawley <crawley@dstc.edu.au> writes:
>
> > I can confirm that there really is a problem running some of the Mauve
> > security testlets under the latest Kissme, Classpath and Mauve. It appears
> > to be a Kissme class loading problem, rather than the fault of the Classpath
> > security implementation. I'm trying to get to the bottom of it ...
The "bottom of it" is that the problem was not in Kissme or Classpath
at all!
The problem was that the failing test cases' constructors were not
declared public. On Kissme, this (correctly IMO) caused the call to
'Class.newInstance' to throw an InstantiationException. I have fixed
the Mauve testcases, and add a 'hint' to SimpleTestHarness to point
people in the right direction in future.
Three issues remain:
* There is a bug in the implementation of Class.getConstructor in
the Jikes RVM. It should not return a constructor unless it is
declared as 'public'.
* We need more comprehensive Mauve testcases for the the Java
APIs for reflective programming,
* There is a problem with Kissme's implementation of stack traces
when an exception is thrown in a native method. It is getting
the source line number wildly wrong.
-- Steve
next parent reply other threads:[~2003-04-07 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3istrt1zv.fsf@lyta.haphazard.org>
2003-04-07 16:09 ` Stephen Crawley [this message]
2003-04-07 22:59 ` Raif S. Naffah
2003-04-07 23:32 ` Stephen Crawley
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=200304071608.h37G8siE021877@piglet.dstc.edu.au \
--to=crawley@dstc.edu.au \
--cc=cbj@gnu.org \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=raif@fl.net.au \
/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).