Repository navigation
NativeAOT: Reporting of the exceptions in the event viewer #73998
Description
I compile WinForms application and it crashes with "marshalling not supported", this message is only visible in the WinDbg, but not in the console and not in the EventViewer.
Faulting application name: WindowsFormsApp1.exe, version: 1.0.0.0, time stamp: 0x6090d7e5
Faulting module name: WindowsFormsApp1.exe, version: 1.0.0.0, time stamp: 0x6090d7e5
Exception code: 0x4b1b53b5
Fault offset: 0x0000000000bedd88
Faulting process id: 0x38a8
Faulting application start time: 0x01d740a4363a160b
Faulting application path: ...\WindowsFormsApp1.exe
Faulting module path: ...\WindowsFormsApp1.exe
Report Id: e4b0ae11-b78f-48f7-a3e5-1255eb71649d
Faulting package full name:
Faulting package-relative application ID:
Would be good to have actual error message here as well.
Activity
hez2010 commentedon May 5, 2021
In general the error message will be printed to stderr, but for a
WinExeit will be redirected toNULfor performance by default. You can overwrite the behavior and print it to a specified file via command line:kant2002 commentedon May 6, 2021
@hez2010 This does not works for WinForms application. Or at least this does not works for me. Empty file produced.
hez2010 commentedon May 6, 2021
@kant2002 I've tested your
CoreRTWinFormsTestBedand this approach works for me. Did you forget to put a2before>err.log?Update: it only works in cmd. It won't work if you're using powershell.
hez2010 commentedon May 6, 2021
Or you can use
& .\WindowsFormsApp1.exe 2>&1 | Out-Stringin powershell.Report unhandled exceptions/FailFast in event log
Report unhandled exceptions/FailFast in event log (#98152)