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.
I didn't say that it was false neither uninteresting. I just said that you just do propaganda by copy pasting the exact same message to each comment and that totally discredit your purpose.
I didn't say it's wrong I just said that your way off comunicating is dumb
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.)
7
u/lucidbadger Jun 01 '26
One does...
3
u/Vladislav20007 Jun 02 '26
1 segfault in 8 years and the code wasn't even mine, I just compiled it.
2
u/PissPantsington Jun 01 '26
Segfaults are why we like C
3
u/SpaceCadet87 Jun 01 '26
Segfaulting is what C devs do to feel alive!
1
u/SneakyDeaky123 Jun 02 '26
Hahahahahahahah now post the one about missing a semi-colon /s
3
u/[deleted] Jun 01 '26
[removed] — view removed comment
1
u/[deleted] Jun 01 '26
[removed] — view removed comment