[Mono-dev] 1488 Ways To Break A Runtime

Jim Purbrick jimpurbrick at yahoo.co.uk
Thu Feb 23 19:58:45 EST 2006

New archive here:


I've added tests for assignment compatibility and new
tests for merging stack state based on the
verification type compatibility rules. All the new
tests assembly with mono ilasm and give the expected
errors when run through peverify /IL (although
peverify doesn't seem to like my method pointers, I'm
not sure if I've got something wrong there).

I _think_ these are all the tests that I need to fail
verification for our current use of Mono in Second
Life. I don't think we need tests for other opcodes or
more elaborate tests for call due to our whitelisting
of opcodes and allowable methods. I also think we
might be able to get away without binary tests and
meta data tests as all of the assemblies we load are
generated by mono ilasm which shouldn't generate
broken binaries or meta data (Ankit, does this sound

Anyway, I need to get back to work on SL, so now would
be a good time to put the current set of tests in svn
and for people to check the current tests, add the
missing ones and to get mono to fail all of the tests
when it verifies them.

Thanks for all your help putting the tests together,



To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

More information about the Mono-devel-list mailing list