Access Violation Tracking

[Steven Schveighoffer via Digitalmars-d-learn]

On 11/6/14 10:22 PM, ketmar via Digitalmars-d-learn wrote:
> On Thu, 06 Nov 2014 20:13:02 +0000
> "Nordlöw" via Digitalmars-d-learn <digitalmars-d-learn at puremagic.com>
> wrote:
>
>> On Wednesday, 5 November 2014 at 11:39:21 UTC, Marc Schütz wrote:
>>> If you're on Linux, you can turn SEGVs into Errors:
>>>
>>>      import etc.linux.memoryerror;
>>>      registerMemoryErrorHandler();
>>
>> Why isn't such a useful feature activated by default? Performance
>> reasons?
> 'cause it's not really that useful. uncaught (by the proper checks)
> segmentation fault is the serious bug, program must crach and spit out
> postmortem dump

In an environment that you don't control, the default behavior is likely 
to print "Segmentation Fault" and exit. No core dump, no nothing.

This leads to unhelpful bug reports, and seeing if you can get your 
client to "try to make it happen again with this debug build, or with 
the shell set up to make a core dump".

I think it would be nice to be able to check if a core dump is enabled, 
and if not, register the handler by default.

-Steve