-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
EXC_CORPSE_NOTIFY on macOS Big Sur #1831
Comments
@LaraSQP Thanks for reporting the issue! I did find one issue when using Do you have the .NET stack trace by chance? That crash report appears to be going through .NET code (e.g. |
Thank you for the quick reply. I do not have the stack trace but will ask for it. |
Apologies. How do I get the .NET stack trace? |
I recently discovered that .NET Core doesn't report the .NET stack trace properly in the crash report on macOS. I'll submit a fix for that. The only way to get the report is to run the .app from the command line afaik, e.g. by running the following:
|
You are great. Will try that. |
Darn it. I have not been able to get access to a macOS Big Sur. But you can download Burbridge from here: http://www.sequencepublishing.com/cgi-bin/download.cgi?burbridgemac |
Ah yes, this is what I thought was going on:
This should be fixed in 2.5.7+ with PR #1822. There's a few other issues related to this with |
Much, much appreciated. |
The app has been compiled using netcoreapp3.1 + Eto 2.5.1 and runs fine on Windows, Linux, and Mac.
The app fails to start when running it on a new M1 (Apple Silicon) laptop with .Net Core 3.1 and .Net 5 installed.
Any ideas?
Thank you.
The text was updated successfully, but these errors were encountered: