You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can succesfully emit and run code without document writer. But we see that exception in opposite scenario:
System.ArgumentException : Не удается передать указанный код операции в метод EmitCall.
Имя параметра: opcode
в System.Reflection.Emit.ILGenerator.EmitCall(OpCode opcode, MethodInfo methodInfo, Type[] optionalParameterTypes)
в GrEmit.GroboIL.Emit(OpCode opCode, ILInstructionParameter parameter) в C:\BuildAgent\work\249acc80a2fd7042\GrEmit\GrEmit\GroboIL.cs:строка 2000
в GrEmit.GroboIL.Dispose() в C:\BuildAgent\work\249acc80a2fd7042\GrEmit\GrEmit\GroboIL.cs:строка 147
в GremitBugs.Tests.TestLdftn(Boolean useDocumentWriter) в C:\Users\****\Documents\Visual Studio 2017\Projects\GremitWeaks\GremitBugs\Tests.cs:строка 45
We are trying to emit Ldftn instruction. In some cases we see exception System.ArgumentException.
Look at this code:
We can succesfully emit and run code without document writer. But we see that exception in opposite scenario:
We assume that bug is located here:
gremit/GrEmit/GrEmit/GroboIL.cs
Lines 1999 to 2000 in b08a146
Sometimes MethodILInstructionParameter leads to emit non call opcodes :)
The text was updated successfully, but these errors were encountered: