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.
When building with the unified API, sometimes the compiled method names will be slightly different on 32 and 64-bit iPads. For example:
Namespace_MoreNamespace_ClassName_MethodName on 64 bit
Namespace_MoreNamespace_ClassName_MethodName_0 on 32 bit
This wouldn't matter except that crash reporting tools like HockeyApp will bucket crashes that occur in this method into two different groups, making it more difficult to analyze which crashes are the most common.
Do you have sample crash reports that shows this?
Zoltan, is this something we can do something about?
The _0 suffixes are added to distinguish similar method names from each other, but the aot process is mostly deterministic, so the same methods should get the same symbols in 32 and 64 bit mode. Would it be possible to get a test case for this ?
I added two private attachments. If you can't figure it out just by looking at those source files, let me know and I can try to pare it down to something that compiles.
Fixed in mono master 27fd291b19c50ce81facefb4ea2dac037290b454.
Closing based on comment #8 (that's been shipping in XI for a while)