From: Peter Naulls <peter@erble.freeserve.co.uk>
To: mauve-discuss@sourceware.cygnus.com
Subject: Re: Bytecode verifiers
Date: Wed, 20 Dec 2000 04:49:00 -0000 [thread overview]
Message-ID: <e73adc2f4a%peter@erble.freeserve.co.uk> (raw)
In-Reply-To: <200012201108.eBKB8b402577@kevin.inria.fr>
In message < 200012201108.eBKB8b402577@kevin.inria.fr >
Bernard Serpette <Bernard.Serpette@sophia.inria.fr> wrote:
> Sorry to disturb you, I have a short question which I hope you
> have the answer or at least a pointer to right person.. We are implementing
> a bytecode verifier and we are searching for a collection of classfiles
> in order to test the correctness of our implementation. We are particulary
> interested by "dirty" classfiles (which can be generated by a correct
> compiler) and "tricky" classfile (generated by optimizer or by hand).
>
> In the Mauve libraries, dirty classfiles will be a good suite in
> order to test when "Class.forName" must raises an exception...
>
> So, do you know where we can find this kind of datas ? We still
> don't have answers from JCK... By the way, we will happy to contribute
> to Mauve project by providing our local dirty classfiles.
First of all, I'd be very happy to see such tests in Mauve, as I use it
quite a bit to test my JVM.
It's not entirely clear what you're asking here (to me at least) - you
say you've got some dirty classes, but you also want some more classes?
One of the problems here is that Mauve is really only a test of the
library implementation - it doesn't (but perhaps should) target weak
spots in JVMs; it's not really organised in a manner suitable for this
- the tests are arranged in terms of library functionality, not JVM
functionality.
Peter
--
------------------------------------------------------------------------
Peter Naulls - peter@erble.freeserve.co.uk
Homepage - http://free.prohosting.com/~chocky/
Java for RISC OS and ARM - http://free.prohosting.com/~chocky/java/
Debian Linux on RiscPCs - http://www.erble.freeserve.co.uk/
------------------------------------------------------------------------
next prev parent reply other threads:[~2000-12-20 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 3:08 Bernard Serpette
2000-12-20 4:49 ` Peter Naulls [this message]
2000-12-20 9:51 ` Tom Tromey
2000-12-20 15:01 ` Peter Naulls
2000-12-21 21:48 ` tests that pass but indicate an error? Brian Jones
2000-12-21 22:11 ` Tom Tromey
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=e73adc2f4a%peter@erble.freeserve.co.uk \
--to=peter@erble.freeserve.co.uk \
--cc=mauve-discuss@sourceware.cygnus.com \
/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).