-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Bad data can cause ILVerify to throw NRE #63221
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
This is caused by |
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsDescriptionWhile attempting to use ILVerify to diagnose a compiler output problem, it instead blew up in my face, dumping a Reproduction Steps
Expected behaviorA correct program should not throw "boneheaded exceptions." A diagnostic tool should provide helpful diagnostic information about the nature of errors encountered. Actual behavior
Configuration.NET 5, Windows 10, x64
|
Duplicate of #62711 |
Is there some nightly feed with a fix for this issue available? |
Yes, it should be in the nightly dotnet7 feed.
It is prerelease package so you need to specify |
Description
While attempting to use ILVerify to diagnose a compiler output problem, it instead blew up in my face, dumping a
NullReferenceException
stack trace on me.Reproduction Steps
ilverify .\testcase.dll -r "C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.13\*.dll"
(Adjust .NET 5 path as needed)Expected behavior
A correct program should not throw "boneheaded exceptions."
A diagnostic tool should provide helpful diagnostic information about the nature of errors encountered.
Actual behavior
Configuration
.NET 5, Windows 10, x64
The text was updated successfully, but these errors were encountered: