On 2012-03-06 13:48, Chad J wrote:
On 03/06/2012 02:54 AM, Jacob Carlborg wrote:
On 2012-03-06 08:53, Jacob Carlborg wrote:
On 2012-03-06 03:04, Steven Schveighoffer wrote:
Certainly for Mac OS X, it should do the most informative appropriate
thing for the OS it's running on. Does the above happen for D programs
currently on Mac OS X?
When an exception if thrown and uncaught it will print the stack trace
to in the terminal (if run in the terminal). If the program ends with a
segmentation fault the stack trace will be outputted to a log file.
Outputting to a log file is handle by the OS and not by druntime.
It sounds like what you'd want to do is walk the stack and print a trace
to stderr without actually jumping execution. Well, check for being
caught first. Once that's printed, then trigger an OS error and quit.
I'm just writing how it works, not what I want to do.
--
/Jacob Carlborg
