Bug 18187 - Debugging async code follows continuation instead of going to next line
Summary: Debugging async code follows continuation instead of going to next line
Status: RESOLVED FEATURE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.10.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: 3.9
Assignee: vsx
URL:
Depends on:
Blocks:
 
Reported: 2014-03-05 09:31 UTC by René Ruppert
Modified: 2016-05-10 17:05 UTC (History)
9 users (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 on Developer Community 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:
Status:
RESOLVED FEATURE

Description René Ruppert 2014-03-05 09:31:25 UTC
I'm debugging an async method by stepping over. If I hit a line that uses "await", the debugger jumps to the end of the method I'm currently in. If I continue with stepping over, I will follow the code that is the continuation of the task I'm awaiting.
Is that by design? I expected to continue debugging in the next line after the "await", just as if the code was synchronous.

If I put a breakpoint into the next line and let the code run, it will eventually hit the breakpoint, so this works.
Comment 1 Ram Chandra 2014-03-05 12:20:02 UTC
I have checked this issue and i am able to reproduce this issue with the above bug description.

screencast: http://www.screencast.com/t/2vrrT5PJFv

Environment:

Windows 7
VS2013
Xamarin.Android : 1.10.39
Comment 2 Jose Gallardo 2014-11-14 11:54:31 UTC
This is by design.