Bug 32918 - StackTrace() missing original exception - ExceptionDispatchInfo
Summary: StackTrace() missing original exception - ExceptionDispatchInfo
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib (show other bugs)
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 4.2.0 (C6)
Assignee: Bugzilla
Depends on:
Reported: 2015-08-10 13:35 UTC by Joe Pro
Modified: 2015-08-17 10:31 UTC (History)
6 users (show)

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

repro (1.33 KB, text/plain)
2015-08-10 13:35 UTC, Joe Pro

Description Joe Pro 2015-08-10 13:35:27 UTC
Created attachment 12434 [details]

When building a StackTrace object from an exception re-thrown by ExceptionDispatchInfo, the original exception stacktrace is gone even though it is included in the Exception.  See simple repro attached.  When running repro on windows, against the .net framework, the full stacktrace is available.
Comment 1 Joe Pro 2015-08-10 13:47:10 UTC
The repro is clearly not for XI because I don't have access to it at the moment, but it should be easy to adapt it :)
Comment 2 Rolf Bjarne Kvinge [MSFT] 2015-08-11 07:07:47 UTC
@Marek. this looks like something in the BCL.
Comment 3 Marek Safar 2015-08-17 10:31:02 UTC
Fixed in master and 4.2 branch

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.

Create a new report for Bug 32918 on Developer Community or GitHub if you have new information to add and do not yet see a matching report.

  • 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

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.

Related Links: