Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Source line breakpoints stop working when tiered jitting replaces the code #14423
If you set a breakpoint in your source code and then execute that code over and over, eventually (after 30+ iterations currently) the breakpoint will stop triggering. What occurs is that the tiered compilation feature replaced the original jitted code with the breakpoint with new code, and the new code has no breakpoint. That in turn occurs because the JITComplete callback only triggers for the first jitting of a method, but doesn't trigger for subsequent jittings:
In order to place breakpoints in all jitted versions of the method, the debugging layer must be informed that these new versions exist.