Bug 36794 - Improve or provide stacktrace unwinding option for devices API 15 and lower
Summary: Improve or provide stacktrace unwinding option for devices API 15 and lower
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler (show other bugs)
Version: 6.0.0
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Marek Habersack
URL:
Depends on:
Blocks:
 
Reported: 2015-12-09 22:24 UTC by Peter Collins
Modified: 2016-09-05 14:35 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Peter Collins 2015-12-09 22:24:56 UTC
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?
Comment 1 Alex Rønne Petersen 2016-04-12 04:02:25 UTC
What we will likely do, if anything, is bundle libunwind with XA. I don't know when we'll look into that though.
Comment 3 Ludovic Henry 2016-09-05 14:35:50 UTC
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.