Access Violation Tracking

[Steven Schveighoffer via Digitalmars-d-learn]

On 11/11/14 10:14 AM, Kagamin wrote:
> On Friday, 7 November 2014 at 03:45:23 UTC, Steven Schveighoffer wrote:
>> In an environment that you don't control, the default behavior is
>> likely to print "Segmentation Fault" and exit. No core dump, no nothing.
>
> If you let the exception propagate into OS, by default Windows creates
> memory dump.

Windows is a different story. You actually get a reasonable result.

On Unix flavors, you get a signal, and by default, an exit, with the 
following message:

Segmentation fault
prompt>

No history, no core dump (generally this is off by default), no 
information as to where it occurred, why it occurred. Nothing.

-Steve