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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
If I enable LLVM in my release build, I get the following Assertion failure and subsequent build failure (mtouch exited with code 1):
AOT Compilation exited with code 134, command:
MONO_PATH=/Users/pseabury/Projects/SO_11385906/SO_11385906/bin/iPhone/Release/SO_11385906.app /Developer/MonoTouch/usr/bin/arm-darwin-mono --llvm --aot=mtriple=armv6-darwin,full,static,asmonly,nodebug,llvm-path=/Developer/MonoTouch/LLVM/bin/,outfile=/var/folders/mt/b7h3_pgs3lxgpvpm2h1_2ppc0000gn/T/tmp3f6bfe89.tmp/ServiceStack.Text.MonoTouch.dll.6.s "/Users/pseabury/Projects/SO_11385906/SO_11385906/bin/iPhone/Release/SO_11385906.app/ServiceStack.Text.MonoTouch.dll"
Mono Ahead of Time compiler - compiling assembly /Users/pseabury/Projects/SO_11385906/SO_11385906/bin/iPhone/Release/SO_11385906.app/ServiceStack.Text.MonoTouch.dll
* Assertion at ../../../../../mono/mono/mini/mini-llvm.c:4535, condition `LLVMTypeOf (values [sreg1]) == LLVMTypeOf (values [phi->dreg])' not met
Self-contained test case attached. The sample code links to latest ServiceStack binaries, but if it makes debugging easier you can just use the main branch source for both ServiceStack & ServiceStack.Text.
Related StackOverflow question here http://stackoverflow.com/questions/11385906/ .
Zoltan, this looks like your area.
Can't reproduce this using master.
I can confirm this is fixed in master (i.e. 5.3.5 when it is released), and it crashes with 5.2.
*** Bug 4381 has been marked as a duplicate of this bug. ***