Bug 2687 - Full paths for stack traces not displayed in debuggers exception dialog
Summary: Full paths for stack traces not displayed in debuggers exception dialog
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-29 10:54 UTC by Jackson Harper
Modified: 2012-01-06 14:24 UTC (History)
1 user (show)

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

screenshot of stack with some line numbers (47.96 KB, image/png)
2011-12-29 10:55 UTC, Jackson Harper

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 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.

Related Links:

Description Jackson Harper 2011-12-29 10:54:58 UTC
See attached screenshot. AFAICT there is no way of resizing and seeing more line number info.

(yes I know I can get it under the details tab, just seems like the full paths should be in the initial view too).
Comment 1 Jackson Harper 2011-12-29 10:55:18 UTC
Created attachment 1108 [details]
screenshot of stack with some line numbers
Comment 2 Jeffrey Stedfast 2012-01-06 14:24:48 UTC
Ugh, looks like a side-effect of my patch a month or 2 ago to ellipsize "long" strings from the debugger.

Made it so that exception dialogs disable that evaluation option.