Bug 44341 - No way of updating async method local variables
Summary: No way of updating async method local variables
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger (show other bugs)
Version: 4.7.X
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
Depends on:
Reported: 2016-09-15 02:29 UTC by David Karlaš
Modified: 2016-09-22 14:07 UTC (History)
2 users (show)

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


Description David Karlaš 2016-09-15 02:29:14 UTC
Async method local variables are implemented as fields on compiler generate *struct* problem is that IDE side obtains this value via CMD_STACK_FRAME_GET_THIS command. Hence there is no way to update this struct fields...
Comment 1 Zoltan Varga 2016-09-21 19:48:56 UTC
Comment 2 Zoltan Varga 2016-09-22 14:07:56 UTC
Added a SetThis method to StackFrame () to support this in e0f96a41c6b60b8c4dc5389e4cf9b906e3b26f75.

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the 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.

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