On Sun, Mar 26, 2017 at 7:21 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:

On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote:
>
> > On 26 Mar 2017, at 15:40, Peter Uhnak <i.uhnak@gmail.com> wrote:
> >
> > Hi,
> >
> > is it possible to use UFFI and avoid crashing the image when the called code segfaults?
> >
> > In other words, can I somehow wrap the call and throw in-image Exception/Error on failure instead of the whole thing crashing?
>
> that��s not possible, once you segfault, you segfault.

Ah, ok.

Well, you can capture the signal, but the problem is not the signal itself but what caused the problem. The most common case of segfaut is memory corruption (and thus a program that tries to wrongly interpret wrong addresses). If you already corrupted the memory doing something wrong, how can you "fix it"?

��

>
> > Or is the only way to do that have the called thing running as a separate app (e.g. via OSSubProcess) and communicate via pipes or sockets?
>
> that��s not done.
> no idea how much effort is required to implement, but I imagine is not trivial.

Nono, I didn't mean making UFFI calls via socket (although that would be interesting), but rather making a C app that would make the calls, and that would provide a socket interface. (Which is what I typically do with other langs).

Thanks,
Peter