Spec#, nullables and more

Kagamin spam at here.lot
Sun Nov 7 11:23:17 PST 2010


FeepingCreature Wrote:

> This means stack traces are out unless you have special handling for segfaults that decodes the stack and prints the error pos. That in turn means you need to have a debugger attached to get stacktraces, which can be annoying especially in long-running programs where the crash is often the first indication you have of a problem.
> 
Doesn't it write coredump, which can be investigated later?


More information about the Digitalmars-d mailing list