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.
Key info looks to be that the behavior is not reproducible when enabling llvm in a template, and that the crash started occurring with fa4ebc0b71dec0c099157cad69c4c9f08d5dfaf0.
hmm... did it start at fa4ebc0b71dec0c099157cad69c4c9f08d5dfaf0
or was it the last working revision ?
because the next commit was an LLVM bump
I get different errors in both revs :(
When getting a crash report always go see the device's console logs. If the crash can't be symbolicated then the logs might have the only clue we can use.
This work with bf7dd0a1c64321f0c6b951749f993a1c9a6f01b5 (184.108.40.206) which has the latest LLVM bump that Zoltan made on master-3.0
LLVM tests passing now on eg. 220.127.116.11: https://wrench.internalx.com/Wrench/ViewLane.aspx?lane_id=640&host_id=75&revision_id=188040