http://d.puremagic.com/issues/show_bug.cgi?id=4385
Summary: Uncaught exceptions should dump a core
Product: D
Version: D1 & D2
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: druntime
AssignedTo: s...@invisibleduck.org
ReportedBy: llu...@gmail.com
--- Comment #0 from Leandro Lucarella <llu...@gmail.com> 2010-06-24 17:43:57
PDT ---
Right now an uncaught exception just prints the exception name (or the
backtrace in the better case) and make the program exit with status 1.
This is really bad for debugging purposes, and specially harmful for the assert
statement. I find the assert statement close to useless because this
limitation, because I can't inspect the dead program to see what happened as
one usually do with C++ (which calls abort when there is an uncaught exception,
resulting in a core dump).
I'm finding myself removing asserts (specially when they test for null
pointers, as the null pointer gives me a dump eventually) or doing a custom
assert that calls C's abort().
PS: I'm marking this as a druntime issue even when applies to D1 because it is
a runtime issue (and maybe nobody wants to touch Phobo's 1 runtime).
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
