Bug 10589 - Support thread current lines in VS debugger
Summary: Support thread current lines in VS debugger
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 3.0
Hardware: PC Windows
: Normal enhancement
Target Milestone: Future Cycle
Assignee: Joaquin Jares
Depends on:
Reported: 2013-02-22 14:15 UTC by Eric Maupin
Modified: 2017-06-28 17:09 UTC (History)
10 users (show)

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

Screenshot of the feature (23.56 KB, image/png)
2013-02-22 14:15 UTC, Eric Maupin

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 10589 on Developer Community 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
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:

Description Eric Maupin 2013-02-22 14:15:29 UTC
Created attachment 3457 [details]
Screenshot of the feature

In Visual Studio there's a feature to display a marker next to the current lines that are being executed by other threads when paused. Despite being enabled, we do not currently support this feature.
Comment 1 Juan Marcelo Tondato 2016-12-23 18:27:39 UTC

As we've added several improvements to our debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.

That said, if you're still facing this issue with current bits, please feel
free to reopen the bug.
Comment 3 Joaquin Jares 2016-12-28 11:20:29 UTC
I interpreted this bug incorrectly. I understood with the screencast. Moving to C10 for resolution there.
Comment 4 Joaquin Jares 2017-06-28 17:09:49 UTC
We're focusing on quality right now. As soon as we get back to features I'll look into this.