I don't know who was the fucking moron who decided how much detail should go in the classic "Segmentation fault (core dumped)" message, but they should be kidnapped and tortured. And no one should tell them why they're getting kidnapped and tortured. Just let the fucker guess.

Apply debugger? Segfault handling isn't easy because the cause could be so many things, so the OS just sends a signal and basically gives up.

@RememberMe It just happened to me in .NET Core. That's not event C or C++. Maybe the backend has stuff written in one of those languages, but that's not my code. This is C# for fucks sake, there should be no fucking segfault.

Maybe it detects today's date and that's why it's trying to fuck me in the ass. Not funny at all.

I can relate to this. Why the fuck would you just output segmentation fault and not tell where it happened? Even debugging takes a good amount of your time, and you want to pull out your hair before you finally find out where the problem is coming from.