Repository navigation
System.AccessViolationException: Int128 ToString invalid memory reads and string interpolation crash #75656
Description
Description
When I to .ToString() on my Int128, it reads out memory and then crashes.
When I do string interpolation on my Int128, it throws an exception and crashes.
Clearly, this is not intended functionality.
Reproduction Steps
- Run
Console.WriteLine(new Int128(18446744073709551613, 18446744073709551604).ToString());- Run
Console.WriteLine($"A={new Int128(18446744073709551613, 18446744073709551604)})");(This is literally my whole program now because I wanted to make sure it wasn't something else)
Expected behavior
Prints a number and doesn't crash ;)
Actual behavior
-
Prints random memory and crashes
-
Crashes
Regression?
No response
Known Workarounds
No response
Configuration
.NET 7 RC 1
Windows 10 x64 v10.0.19044.1949
Running in Debug mode
Also tested on macOS 12.6 x64 with .NET 7 Preview 7, got slightly different output (below):
Other information
It's probably missing a \0 at the end based on that ridiculous console output. idk. Also unsure if the string interpolation one has a secondary issue as well or not.
Edit: it (above) being one of the helper method that converts to a string. This could be why since it may just keep reading random memory when constructing the string until it hits a \0 char (ie. 2x 0 bytes - low chance hence why I see AVEs instead) or an AVE/NRE.
Activity
tannergooding commentedon Sep 15, 2022
Pretty sure this has already been fixed for RC2, but I will confirm first thing tomorrow.
#74536 would be the likely fix that was done for it.
hamarb123 commentedon Sep 15, 2022
Okay, so I would have to download a daily build to be able to test my actual code without this. Would the current daily build be new enough?
tannergooding commentedon Sep 15, 2022
Yes, I expect the current daily build should contain the relevant fix.
hamarb123 commentedon Sep 15, 2022
I've tested it, and it is fixed in the daily version, thanks!
Also, (unrelated to this issue), is there a way to get the sdk installer not to do this (I assume it's removing the previous version)?
tannergooding commentedon Sep 15, 2022
I think @KathleenDollard or @baronfel would be the people to answer that.
I'll close this issue since the issue is resolved in the latest daily build for .NET 7 RC2.
baronfel commentedon Sep 16, 2022
We typically only keep one version of the SDK from each 'feature band', meaning the last number's hundreth'-place. So depending on which 'channel' you've installed an SDK from (typically standalone installer MSI or VS are the main channels), if you install a newer version in the same feature band within that channel, the previous installation will be removed. So if you really wanted to make it happen, you could install a version of VS that included the preview you wanted, and install the standalone installer of the other version you wanted.
Having said all of that, you can also use the dotnet-install scripts to install any version to any location at any time, setting the
DOTNET_ROOTto point to that installed location.