Skip to content
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

System.TypeInitializationException during expression evaluation #779

Closed
caslan opened this issue Sep 23, 2016 · 3 comments · Fixed by #986
Closed

System.TypeInitializationException during expression evaluation #779

caslan opened this issue Sep 23, 2016 · 3 comments · Fixed by #986

Comments

@caslan
Copy link
Contributor

caslan commented Sep 23, 2016

This failure stack is the top most non fatal error we are encountering in the debugger. It should have something to do with OpenSSL dependency on OSX but we need to investigate further to see if this is an issue external to debugger or not:

at Interop.Crypto.EvpSha1()#N# at Internal.Cryptography.HashProviderDispenser.CreateHashProvider(String hashAlgorithmId)#N# at System.Security.Cryptography.SHA1.Implementation..ctor()#N# at System.Security.Cryptography.SHA1.Create()#N# at Roslyn.Utilities.SHA1CryptoServiceProvider..ctor()#N# at Microsoft.CodeAnalysis.CryptographicHashProvider.ComputeSha1(Byte[] bytes)#N# at Microsoft.CodeAnalysis.AssemblyIdentity.CalculatePublicKeyToken(ImmutableArray`1 publicKey)#N# at Microsoft.CodeAnalysis.AssemblyIdentity.get_PublicKeyToken()#N# at Microsoft.CodeAnalysis.AssemblyIdentity.KeysEqual(AssemblyIdentity x, AssemblyIdentity y)#N# at Microsoft.CodeAnalysis.AssemblyIdentity.MemberwiseEqual(AssemblyIdentity x, AssemblyIdentity y)#N# at Microsoft.CodeAnalysis.AssemblyIdentityComparer.TriviallyEquivalent(AssemblyIdentity x, AssemblyIdentity y)#N# at Microsoft.CodeAnalysis.AssemblyIdentityComparer.Compare(AssemblyIdentity reference, String referenceDisplayName, AssemblyIdentity definition, Boolean& unificationAppl

@gregg-miskelly
Copy link
Contributor

This issue is also tracked with dotnet/roslyn#12681

@gregg-miskelly
Copy link
Contributor

gregg-miskelly commented Nov 18, 2016

This is still our top error hit. Lets see if we can fix this for 1.6. My thought is, on OSX, disable the installation of the debugger unless we find openssl.

@gregg-miskelly
Copy link
Contributor

NOTE: This work around will go away once the debugger is running on https://github.com/dotnet/corefx/issues/9394

@gregg-miskelly gregg-miskelly self-assigned this Nov 22, 2016
gregg-miskelly added a commit to gregg-miskelly/vscode-csharp that referenced this issue Nov 22, 2016
By far our most common EE error is due to folks not having the OpenSSL symlinks created. This checkin adds detection logic so that we will not install the debugger unless they are present.

This resolves dotnet#779
gregg-miskelly added a commit to gregg-miskelly/vscode-csharp that referenced this issue Nov 23, 2016
By far our most common EE error is due to folks not having the OpenSSL symlinks created. This checkin adds detection logic so that we will not install the debugger unless they are present.

This resolves dotnet#779
gregg-miskelly added a commit that referenced this issue Nov 24, 2016
By far our most common EE error is due to folks not having the OpenSSL symlinks created. This checkin adds detection logic so that we will not install the debugger unless they are present.

This resolves #779
WardenGnaw pushed a commit to WardenGnaw/omnisharp-vscode that referenced this issue Nov 29, 2016
By far our most common EE error is due to folks not having the OpenSSL symlinks created. This checkin adds detection logic so that we will not install the debugger unless they are present.

This resolves dotnet#779
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants