On 10.05.2009 00:05, mpt wrote:
I keep making 2 mistakes in my D programs, and fixing them feels
troublesome.
1. Null references. I get a segfault and gdb is useless (ldc thing maybe).
2. Exceptions. It prints the msg nicely, but it's unhelpful in tracing
the real cause of error.
Shouldn't there be an automatic null check for references and stack
traces? Sometimes I think I'm using the wrong tool as others have
solutions for these.
Tango trunk has stacktrace functionality for both Windows and linux I
think. There's also a Phobos backtrace patch.
