Bug 42366 - Exception doesn't include Java native stacktrace anymore
Summary: Exception doesn't include Java native stacktrace anymore
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries (show other bugs)
Version: 6.1.0 (C7)
Hardware: PC Mac OS
: High major
Target Milestone: 6.1.x (C7SR1)
Assignee: Jonathan Pryor
Depends on:
Reported: 2016-07-05 19:28 UTC by Jérémie Laval
Modified: 2016-07-18 12:36 UTC (History)
5 users (show)

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


Description Jérémie Laval 2016-07-05 19:28:45 UTC
With the switch to the referencesource version of System.Exception, the behavior of .ToString has changed[1][2] and doesn't query anymore the `StackTrace` property overload of Java.Throwable which include Java stracktrace information.

As a result, the Java native stacktrace isn't displayed by default anymore when printing an exception or inspecting it under debugger.

[1]  https://github.com/mono/mono/blob/mono-4.4.0-branch/mcs/class/corlib/System/Exception.cs#L277
[2]  https://github.com/mono/mono/blob/master/mcs/class/referencesource/mscorlib/system/exception.cs#L489
Comment 2 Jonathan Pryor 2016-07-07 16:59:35 UTC
Fixed in monodroid/9ce53701.
Comment 3 Abhishek 2016-07-08 13:50:55 UTC
I have checked this issue and able to reproduce this issue at my end with following build: xamarin.android-6.1.99-342_0be581dc4ee4cdb9d06c8ffd0b7ad9b3cfd02d98.

Application Output: https://gist.github.com/Abhishekk360/1718690825d8d3e1aac3edf315599371

To verify this issue I have checked this issue with latest master build provided in the trello card:

I am unable to check the behavior due to this bug https://bugzilla.xamarin.com/show_bug.cgi?id=42425. Once this issue will be resolved I will verify this issue at my end.

Comment 4 Abhishek 2016-07-08 13:59:23 UTC
An Update to above issue I have missed to add the screencast: http://www.screencast.com/t/qWA3JOVUe

Comment 8 abhi 2016-07-18 12:36:03 UTC
As per comment 7 I am making this issue is verified fixed.

Note You need to log in before you can comment on or make changes to this bug.