Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 52735 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 19941 [details]
generated il code
Part of il(emit) generated code attached.
The defect appears only in release mode(if start .exe with '--debug=mdb-optimizations', app will be work correctly).
this code throw exception with message: " Error feeding module: Field "xxx.TradeMessage.aggressorSide", bound to xxx.Messages.AggressorSide (underliing type is System.Int32), cannot contain unsupported value 255 of enum xxx.Messages.AggressorSide. This value is out of supported range."
can see(from attached il src) exception mean that 'AggressorSide_6' local variable has '255' value. but 'AggressorSide_6' local variable was assigned with SByte value[-128;127].
method ReadEnumInt8() from which was taken SByte can be represented as (with simplifications):
return (SByte)byteArray[i]; //where byteArray is byte
It looks like mono skip Byte to SByte convertion.