Hi Do you have a link where I could read about this? (or could you explain quickly?) :) I added them around my method processing and it works fine. PEVerify seems happy (except for the 19 stack-related errors I now have;)). Now my next step is to keep track of the argument stack. You mentioned Mono.Decompiler for that, will look into it.
Br, Tedd -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jb Evain Sent: 27. mars 2010 00:31 To: [email protected] Subject: Re: [mono-cecil] Bug? Hey, On 3/26/10, Tedd Hansen <[email protected]> wrote: > Could use some input on > http://teddhansen.wordpress.com/2010/03/20/bug-in-mono-cecil/ > Is it a bug? If not, how do I ensure correct pos? I added a comment on the blog when this was posted, but somehow it got removed. It's not a bug, you're injecting too much code into a short form branch. If you don't want to deal with it manually, call: method_body.Simplify () before instrumenting. That will transform all short forms to normal forms. And when're you're done you can call: method_body.Optimize () to turn them back to short forms if possible. Here, "bug" is gone. -- Jb Evain <[email protected]> -- -- mono-cecil To unsubscribe from this group, send email to mono-cecil+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject. -- -- mono-cecil To unsubscribe from this group, send email to mono-cecil+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
