From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Naulls To: mauve-discuss@sourceware.cygnus.com Subject: Re: Bytecode verifiers Date: Wed, 20 Dec 2000 04:49:00 -0000 Message-id: References: <200012201108.eBKB8b402577@kevin.inria.fr> X-SW-Source: 2000-q4/msg00008.html In message < 200012201108.eBKB8b402577@kevin.inria.fr > Bernard Serpette 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/ ------------------------------------------------------------------------