I'm currently trying to work out what is wrong with
some assemblies I've generated and thought that people
on the list might have some cunning techniques that I
haven't thought of.
Currently my process consists of running my app which
embeds Mono, waiting for it to spit out an
**ERROR**:Invalid IL code at <blah> aborting...
message and then staring at dissassembly trying to
work out stack states on a piece of paper and hoping I
see what's wrong.
Are there any better ways? I briefly tried using MS
ildasm to generate CIL from my DLL, tacking on a Main
method which called the broken method then assembling
it with debugging information which let me step
through the CIL in DbgClr, but when I tried to step in
to the busted method DbgClr just told me that the
method was busted and stopped.
Any other ideas?
Cheers,
Jim.
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
