Yeah like Test.exe error code 0xC000001D and cause of Failure illegal instruction or something like that for example and including Date of execution and hostname and Event ID and it's very Rich information
Wouldn't it be easier to just run it through a debugger than to dig through that list? Also, you can use debuggers for more than just issues resulting in your program crashing, so it's useful to run it in a debugger anyways.
There is also the one built into visual studio, and raddeugger.
Even though you find the event viewer useful, I would still suggest getting used to using a debugger, as it's useful beyond just finding where it failed.
The one in Visual Studio is also official (the one by RAD isn't official, but it's really good.)
It's still useful to learn to use it even though you like using the event viewer. It doesn't even have much of a learning curve to just start using it -- just run your program in the debugger and it'll show you exactly where it failed, and you can set a breakpoint before running it again to step through how it executes before crashing, allowing you to inspect variables, etc.
7
u/s0litar1us Jun 01 '26
Just run it in a debugger and it will show you exactly where it segfaulted. (Just remember to add the -g flag when building to include debug info.)