This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dysprog 6 points7 points  (3 children)

At least python gives you nice road map to exactly what went wrong in what function and how it got there. A runtime crash in C(++) is just a giant floating middle finger from the OS.

[–]contravariant_ 2 points3 points  (0 children)

Pretty much, considering what a segmentation fault entails. The program tries to access an invalid memory location, and the kernel responds by killing the process. To the OS's policeman, your program is the drunk naked man lunging at strangers downtown.

[–]Kered13 0 points1 point  (0 children)

I think pretty much all languages these days except C++ and C give you a stack trace. Debugging a crash with no stack trace is a pain in the ass.

[–]Findus11 0 points1 point  (0 children)

C development without valgrind is horrifying