>Here's a great article I'll link to in a second, it might help for you to read a thing or two because you seem to think some problems are unsolvable. There's

>Here's a great article I'll link to in a second, it might help for you to read a thing or two because you seem to think some problems are unsolvable. There's plenty of ways to trace a segfault. One way is not intrinsic to the language and it involves recompiling the program via asan. Without this, you can literally have a memory error but no segfault. The segfault just doesn't occur at all out of pure chance. This basically makes it so there's no direct way. There are ways, but none of them direct, as I said. Virtual memory tricks isn't a direct way. Creating non zero cost abstractions to debug the fault is not direct. I'm sorry. >You may or may not get a correct stack trace depending on where the error occurred. This is a moot point. If you're using libraries, there will be untraceable bugs. Period. No matter the language. Minified javascript is still more traceable then a C++ lib. As I said though the point of the stack trace in JS is the end point of a direct datapath to where the undefined was generated. You can follow the logic backwards via just your brain OR use breakpoints to check the state along each section of the path. >And by the way your attacks on my experience are great. I feel like you're insinuating that I've lied about my experience because that might be a projection of your own experience? If that's the case, I'm sorry to tell you, most people are honest and don't go lying on hacker news for internet points. Once again, you're probably like 15 or 16, we've all been there. You'll grow out of the clout chasing don't worry :) Except I'm not. I think you're the one not being honest here.