On 9/1/11 7:17 PM, Martin Nowak wrote:
Well I agree that segfaults are way more informative than throwing an AssertError. It does have less issues with incorrect stack unwinding and the core file still contains register data. This is biased somewhat by using FreeBSD. I never get stack traces for exceptions but always a core dump.
This behavior could also be enabled by providing a way to provide a custom trace handler. By default, an AssertError would be thrown (or whatever deemed appropriate), but druntime could include an implementation which does the OS-specific things to invoke a debugger/cause it to break.
I don't know the details about the aforementioned assertion call stack »issue« though (druntime's setTraceHandler is currently disabled because of it) – Walter, Sean, et al., could you comment on whether a trace handler like described above would be feasible?
David
