On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:

2017-03-27 11:34 GMT+02:00 Guillermo Polito <guillermopolito@gmail.com>:
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"?

I think important case here is creating wrappers for new C libraries. Common mistake is passing wrong structures to foreign function. Then image crashes and you need restart it and recover code - big waste of time and losing smalltalk liveness.

But then the problem is on "how to not lose your code", not in FFI...��