-
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
corerun needs better error messages #7509
Comments
This error is for Unix only. How about adding a "PAL initialization failed" |
I think that such high level messages would not help in any of the cases people hit from time to time. If we wanted to generate helpful error messages, we would need to do that deep in the bowels of the coreclr runtime and PAL at all places we generate an error, because that's the only place where we really know why the specific error actually happened. The amount of code exercised during the initialization is large, so there are potentially many places that would need to be investigated and an error message generated. And in some cases, the error code even comes from managed code, like e.g. the above mentioned code 0x80131534 which is COR_E_TYPEINITIALIZATION and which means that there was an unhandled exception during type initialization. |
Another option might be to recognize an environment variable analogous to the host's COREHOST_TRACE. When this is set, we write to console at places that historically have caused initialization failures. We can add more progressively as needed. The perf cost in the normal case would hopefully be low - a bunch of boolean checks and some code size. The goal simply being to help customers unblock themselves. |
Happens when I run a self contained app as non-sudo. Running as sudo I do not get the error. Latest .NET core 2.2, Linux x64, Ubuntu 18.04. Even hello world app has the issue. |
Often I see
or similar. This is very unfriendly. Corerun should provide better root cause error messages so you're not required to fire up a debugger to track down every configuration "mistake".
The text was updated successfully, but these errors were encountered: