Why CrashRpt could not catch the Crash information for .NET Core?

[diehell02]

I found a problem that a cpp crash catcher tool could not work on .NET Core.
It was work fine on .NET Framework.

I use C++/CLI to run our native lib, and when the crash occurs, CrashRpt will catch the crash info by Windows System Message.
But on .NET Core, the console will print the crash information, like this:

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Repeat 2 times:
--------------------------------
   at <Module>.NativeCppDemo.MyNativeCppTestClass.memberFunctionAddFunCrash(NativeCppDemo.MyNativeCppTestClass*, Int32, Int32, Boolean)
--------------------------------
   at ClrCrashTest.ClrTest.memberFunAddCrash(Int32, Int32, Boolean, Boolean)
   at DotNetLib.Lib.Hello(IntPtr, Int32)

And CrashRpt couldn't get the crash information.

Does it seem that the .NET Core runtime intercepts the crash information throw to the Windows system? If so, how could I disable this?

It's very important for us because if this problem could not be solved, we maybe need to downgrade to .NET Framework, it's a very terrible decision.

Please help me.

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.

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I found a problem that a cpp crash catcher tool could not work on .NET Core.
It was work fine on .NET Framework.

I use C++/CLI to run our native lib, and when the crash occurs, CrashRpt will catch the crash info by Windows System Message.
But on .NET Core, the console will print the crash information, like this:

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Repeat 2 times:
--------------------------------
   at <Module>.NativeCppDemo.MyNativeCppTestClass.memberFunctionAddFunCrash(NativeCppDemo.MyNativeCppTestClass*, Int32, Int32, Boolean)
--------------------------------
   at ClrCrashTest.ClrTest.memberFunAddCrash(Int32, Int32, Boolean, Boolean)
   at DotNetLib.Lib.Hello(IntPtr, Int32)

And CrashRpt couldn't get the crash information.

Does it seem that the .NET Core runtime intercepts the crash information throw to the Windows system? If so, how could I disable this?

It's very important for us because if this problem could not be solved, we maybe need to downgrade to .NET Framework, it's a very terrible decision.

Please help me.

Author:	diehell02
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-

[jkotas]

.NET Core calls RaiseFailFastException Windows API in this case. .NET Framework called RaiseFailFastException in number of situations as well, .NET Core may be calling it more situations.

Does CrashRpt tool have a problem with RaiseFailFastException ?

[diehell02]

area

.NET Core calls RaiseFailFastException Windows API in this case. .NET Framework called RaiseFailFastException in number of situations as well, .NET Core may be calling it more situations.

Does CrashRpt tool have a problem with RaiseFailFastException ?

Thanks for your reply.

Yes, CrashRpt maybe not support RaiseFailFastException.
Have any method to stop the behavior of call RaiseFailFastException?
Or would you know how to get the crash call stack by RaiseFailFastException? Because the purpose of us is to get the call stack when the crash occurs.
If CrashRpt does not support it, we need to find a way to get the call stack.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.