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 36794 on
Developer Community or GitHub 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
Taken from https://bugzilla.xamarin.com/show_bug.cgi?id=32714#c0:
Right now we're only able to provide unwound stack traces on API 16+ devices, and it could be helpful when debugging certain failures to provide an opt-in way of getting this information. Is it possible to either include libcorkscrew with the runtime for API 15 devices, or provide some other codepath that works on those devices to produce stack traces?
What we will likely do, if anything, is bundle libunwind with XA. I don't know when we'll look into that though.
I am only trying to figure out the issue of a bug, and it's not even related to libunwind, so reassigning it to default.