[Mono-dev] [SIGNAL] Segfault in native function called by managed code

[Miguel de Icaza]

It is an implementation choice.

Perhaps we could make this configurable, but more often than not, this
indicates a serious issue, and surfacing something so useful as a
AccessViolationException reduces the usefulness of the feature.

On Fri, Sep 4, 2015 at 6:15 AM, Raphael Boissel <raphael.boissel at gmail.com>
wrote:

> Hello,
>
>
> I have one little question on the way mono currently handles/uses the
> SEGFAULT signal on Unix OSes.
>
> Currently, and correct me if I'm wrong, either the segfault has been
> raised by a managed function and in this case it is handled as a
> genuine exception for instance a nullRefException or if it is triggered
> by native code the entire program is stopped and a stacktrace is
> displayed.
>
> However it seems that mono also follow the second behavior for
> native code that has been invoked inside managed code,
> where I would have expected an AccessViolationException.
>
> Is there any specific reasons why this behavior is followed, or is it
> just an implementation choice ?
>
> (sorry about the potential double post I sent it first with a
> non-whitelisted
> e-mail address)
>
> Thanks,
>
> --
> Raphaël 'Shugo' Boissel
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150904/5c582d2f/attachment.html>