We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Firstly, create a simple console application which is only include one other function except Main with a floating point argument.
Then, write simple code and set breakpoints as follows:
class Program { public static float GetSingle(float instance) => instance; static void Main(string[] args) { [breakpoint] var ret = GetSingle(3.14f); Console.WriteLine(ret); } }
The breakpoints is necessary, that is the culprit for the wrong result.
Run it, wait for the program to stop at the breakpoint, and then continue.
The correct output is 3.14.
I use either Core 2.0 or Core 2.2, everything is fine.
But I change it to Core 3.0, the result is going wrong.
So, what might cause the problem?
The text was updated successfully, but these errors were encountered:
Sounds like https://docs.microsoft.com/en-us/dotnet/core/compatibility/corefx#floating-point-formatting-and-parsing-behavior-changed.
Sorry, something went wrong.
This is difference between the behavior with breakpoint set vs. breakpoint not set.
@sdmaclea You have been looking into this class of issues recently. Is this one a known one?
This was fixed by dotnet/coreclr#25958. It was fixed after 3.0 was released, and should be fixed in 3.1.
So far, we have not backported the fix to 3.0.
I'm going to close this. Feel free to reopen if we think there is a strong need to discuss backporting to 3.0.
sdmaclea
No branches or pull requests
Scenario
Firstly, create a simple console application which is only include one other function except Main with a floating point argument.
Then, write simple code and set breakpoints as follows:
The breakpoints is necessary, that is the culprit for the wrong result.
Run it, wait for the program to stop at the breakpoint, and then continue.
The correct output is 3.14.
I use either Core 2.0 or Core 2.2, everything is fine.
![ncore22](https://user-images.githubusercontent.com/24598247/71532852-6f423380-2930-11ea-889b-1f49d9f3e124.gif)
But I change it to Core 3.0, the result is going wrong.
![ncore30](https://user-images.githubusercontent.com/24598247/71532859-7701d800-2930-11ea-9500-7f891e69fa12.gif)
So, what might cause the problem?
The text was updated successfully, but these errors were encountered: