Steven Schveighoffer wrote:
4. Yes, segfault is a loud error, but it's like hearing a gunshot from under water. It's loud, but you have no idea where it's coming from, or whether a null dereference is to blame. An assert is much more useful because it tells you the line of code that fails. And please *please* don't tell me to create a core dump, or use Dr. Watson. Not helpful.
I don't suppose it helps much, but on *nix you can set a signal handler to get the stack pointer, etc, and generate a stack trace from there. I'm pretty sure this is possible on Win32 as well, but it would likely have to be in the SEH code in the runtime.
Sean
