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.
I wasn't able to symbolicate, if you can give suggestions on that I'd appreciate it, I used ATOS and did it by hand but the results didn't mesh and the addresses in the crash stack trace didn't seem to match what was in the console dump.
How am I wrong there are is that apples to oranges?
To symbolicate you'll need the exact dSYM (same build) that match the binary who generated the crash. Otherwise Apple tools won't give you any more detail.
But even when symbolicated the best you'll be able to get is something like:
which provides less details than what MonoTouch is able to give you in the device logs.
> and the addresses in the crash stack trace didn't seem to match what was in the console dump
The small address offset (between the two stack traces) is only how mono and apple report the frames location - but they will point to the same functions. I can ask a runtime guy for a bit-per-bit explanation of the difference if you like.
For the actual crash you're running into, here are two StackOverflow answers which may help you:
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.