← Home ← Back to /g/

Thread 106558858

15 posts 4 images /g/
Anonymous No.106558858 >>106558870 >>106558992 >>106559003 >>106559011 >>106559042 >>106559043 >>106559069
Oh, this is why people like c
Anonymous No.106558870 >>106558901 >>106558924
>>106558858 (OP)
>Segmentation fault

Cniles still haven't figured how to do useful error messages?
Anonymous No.106558901 >>106558919
>>106558870
>program does something naughty
>useful error message
how?
Anonymous No.106558919 >>106558994 >>106559036 >>106559037
>>106558901
It's 2025. Compilers should be able to figure out when I'm about to de-reference a null pointer.
Anonymous No.106558924 >>106558933
>>106558870
If you want runtime insight into where your program went wrong, use a language that holds your hand, like Go, Java, or Python.
Anonymous No.106558933
>>106558924
I am using a modern language and I don't have to deal with this shit.
Anonymous No.106558992
>>106558858 (OP)
Learn to valgrind, Jack.
Anonymous No.106558994
>>106558919
So should the Github Copilot you used to make your code, faggot.
Anonymous No.106559003
>>106558858 (OP)
i'm afraid this is a skill issue
Anonymous No.106559011
>>106558858 (OP)
HAHAHAHAHA got filtered by this.
Anonymous No.106559036
>>106558919
And they literally do, so what is all the kvetching for.
Anonymous No.106559037
>>106558919
>i want the compiler to insert checks before every read to ensure i'm not reading at address zero
okay but what if you're in an embedded system where reading/writing to address zero is perfectly valid? also nullptrs aren't the only place you're not allowed to read from. if you're writing a normal usermode process, chances are you're limited to only your program's memory. should the compiler insert virtual memory access queries in front of every read too then? wouldn't want to segfault, right?
>inb4 add a compiler option for it then
or you could just learn to write code like a White person
sage No.106559042
>>106558858 (OP)
i'm goin to report this rustroon flame war thread
sage No.106559043
>>106558858 (OP)
>literal decade old screenshot
>https://stackoverflow.com/questions/26961755/i-created-this-program-but-its-giving-output-segmentation-error-core-dumped
Shut the fuck up.
Anonymous No.106559069
>>106558858 (OP)
I never understood why we can't just get a stack trace by default if a program seg faults. Shit is retarded as hell to debug otherwise.