-
Notifications
You must be signed in to change notification settings - Fork 5k
Exception after upgrade: An IL variable is not available at the current native IP. #92777
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
Comments
@jaklithn Thanks for the report ... is it possible to create a shareable repro (presumably just a tiny part of your app)? |
Can confirm I see the exact same thing after upgrading to RC1. Happening when starting debugging from both VS and Rider. Would be having a hard time creating a shareable repro. |
@lewing FYI |
Sorry for late reply. I had so many issues with this so I had to focus on surviving. It took me several hours to get my repo working again. It was not enough to target projects back to NET 8 Preview 7. I also had to completely remove the new SDK from my machine. I am happy to have a working situation. I will hesitate to install NET 8 RCX. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsI had a working .NET 8 Perview 7 WebAssembly Blazor application developed in Rider. After installing .NET 8 RC1 I upgraded all my Nuget packages. I read the documentation but found no direct reasons to adapt my code. I upgraded Rider to version 2023.2.2. When launching my application I get: In the console I have this stacktrace:
|
cc @maraf @pavelsavara - please triage and assign milestone accordingly. |
Tagging subscribers to this area: @thaystg Issue DetailsI had a working .NET 8 Perview 7 WebAssembly Blazor application developed in Rider. After installing .NET 8 RC1 I upgraded all my Nuget packages. I read the documentation but found no direct reasons to adapt my code. I upgraded Rider to version 2023.2.2. When launching my application I get: In the console I have this stacktrace:
|
@thaystg your thoughts ? |
This is related to coreclr debugging not wasm debugging. @isadorasophia can you help us with that? |
Tagging subscribers to this area: @tommcdon Issue DetailsI had a working .NET 8 Perview 7 WebAssembly Blazor application developed in Rider. After installing .NET 8 RC1 I upgraded all my Nuget packages. I read the documentation but found no direct reasons to adapt my code. I upgraded Rider to version 2023.2.2. When launching my application I get: In the console I have this stacktrace:
|
I installed VS 17.8.0 Preview 3 to ensure .NET 8 RC2 came in recommended context. |
Uh oh!
There was an error while loading. Please reload this page.
I had a working .NET 8 Perview 7 WebAssembly Blazor application developed in Rider. After installing .NET 8 RC1 I upgraded all my Nuget packages. I read the documentation but found no direct reasons to adapt my code. I upgraded Rider to version 2023.2.2.
When launching my application I get:
System.ExecutionEngineException: Exception of type 'System.ExecutionEngineException' was thrown.
An IL variable is not available at the current native IP. The error code is CORDBG_E_IL_VAR_NOT_AVAILABLE, or 0x80131304.
In the console I have this stacktrace:
The text was updated successfully, but these errors were encountered: