Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EnC: Multi-line active statement span not calculated properly #58179

Closed
tmat opened this issue Dec 7, 2021 · 0 comments · Fixed by #58831
Closed

EnC: Multi-line active statement span not calculated properly #58179

tmat opened this issue Dec 7, 2021 · 0 comments · Fixed by #58831

Comments

@tmat
Copy link
Member

tmat commented Dec 7, 2021

Version Used:
Version 17.1.0 Preview 3.0 [32005.40.main]

Steps to Reproduce:

public class C
{
    static void Main()
    {
        F(() =>
        {
            Console.WriteLine(1); // breakpoint
            Console.WriteLine(1);
            Console.WriteLine(1);
            Console.WriteLine(1);
            Console.WriteLine(1);
            Console.WriteLine(1);
            Console.WriteLine(1);
        });
    }

    static void F(Action a)
    {
        a();
    }
}
  1. Set breakpoint as indicated, F5
  2. Add a few more Console.WriteLine(1); lines.
  3. Continue

Expected Behavior:

The inner active span covers the entire call F(() => { ... });.

Actual Behavior:

image

Similar issue happens when whitespace is changed in the active statements (e.g. it's indented):
image

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 7, 2021
@jinujoseph jinujoseph added Bug and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 9, 2021
@jinujoseph jinujoseph added this to the 17.1 milestone Dec 9, 2021
@davidwengier davidwengier modified the milestones: 17.1, 17.2.P1 Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants