Re: [Pharo-users] using UFFI in non-crashing way

2017-05-07 Thread Ben Coman
On Sun, May 7, 2017 at 7:45 PM, wrote: > On 07/04/17 18:28, Dimitris Chloupis wrote: >> Do you guys received my CPU exceptions solution message ? Because the >> issue you described is already resolved by hardware. Simple and elegant >> solution too >> On Fri, 7 Apr 2017 at 11:03, Denis Kudriashov

Re: [Pharo-users] using UFFI in non-crashing way

2017-05-07 Thread raffaello . giulietti
On 07/04/17 18:28, Dimitris Chloupis wrote: > Do you guys received my CPU exceptions solution message ? Because the > issue you described is already resolved by hardware. Simple and elegant > solution too > On Fri, 7 Apr 2017 at 11:03, Denis Kudriashov > wrote: > > >

Re: [Pharo-users] using UFFI in non-crashing way

2017-04-07 Thread Dimitris Chloupis
Do you guys received my CPU exceptions solution message ? Because the issue you described is already resolved by hardware. Simple and elegant solution too On Fri, 7 Apr 2017 at 11:03, Denis Kudriashov wrote: > > 2017-04-07 8:22 GMT+02:00 Esteban Lorenzano : > > But then the problem is on "how to

Re: [Pharo-users] using UFFI in non-crashing way

2017-04-07 Thread Denis Kudriashov
2017-04-07 8:22 GMT+02:00 Esteban Lorenzano : > But then the problem is on "how to not lose your code", not in FFI... >> >> >> Restarting image is a problem. For any other "smalltalk" problems we got >> suitable debugger but not in that case. > > > Also when image crashed we need to recover all ob

Re: [Pharo-users] using UFFI in non-crashing way

2017-04-06 Thread Esteban Lorenzano
> On 6 Apr 2017, at 10:39, Denis Kudriashov wrote: > > > 2017-04-06 10:37 GMT+02:00 Denis Kudriashov >: > But then the problem is on "how to not lose your code", not in FFI... > > Restarting image is a problem. For any other "smalltalk" problems we got > suitabl

Re: [Pharo-users] using UFFI in non-crashing way

2017-04-06 Thread Denis Kudriashov
2017-04-06 10:37 GMT+02:00 Denis Kudriashov : > But then the problem is on "how to not lose your code", not in FFI... > > > Restarting image is a problem. For any other "smalltalk" problems we got > suitable debugger but not in that case. Also when image crashed we need to recover all objects st

Re: [Pharo-users] using UFFI in non-crashing way

2017-04-06 Thread Denis Kudriashov
2017-03-27 13:01 GMT+02:00 Guillermo Polito : > But then the problem is on "how to not lose your code", not in FFI... Restarting image is a problem. For any other "smalltalk" problems we got suitable debugger but not in that case.

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-27 Thread p...@highoctane.be
On Mon, Mar 27, 2017 at 1:01 PM, Guillermo Polito wrote: > > > On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov > wrote: > >> >> 2017-03-27 11:34 GMT+02:00 Guillermo Polito : >> >>> Well, you can capture the signal, but the problem is not the signal >>> itself but what caused the problem. The

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-27 Thread Guillermo Polito
On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov wrote: > > 2017-03-27 11:34 GMT+02:00 Guillermo Polito : > >> 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 t

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-27 Thread Denis Kudriashov
2017-03-27 11:34 GMT+02:00 Guillermo Polito : > 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 co

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-27 Thread Guillermo Polito
On Sun, Mar 26, 2017 at 7:21 PM, Peter Uhnak wrote: > On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote: > > > > > On 26 Mar 2017, at 15:40, Peter Uhnak wrote: > > > > > > Hi, > > > > > > is it possible to use UFFI and avoid crashing the image when the > called code segfaults? >

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-26 Thread Thierry Goubier
Le 26/03/2017 à 19:21, Peter Uhnak a écrit : On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote: On 26 Mar 2017, at 15:40, Peter Uhnak 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 ca

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-26 Thread Peter Uhnak
On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote: > > > On 26 Mar 2017, at 15:40, Peter Uhnak 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 i

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-26 Thread David T. Lewis
On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote: > > > On 26 Mar 2017, at 15:40, Peter Uhnak 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 i

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-26 Thread Dimitris Chloupis
> Hi, > > is it possible to use UFFI and avoid crashing the image when the called > code segfaults? > > Yes its possible. When I was exploring the means to live code with C++ I came to specific implementations of live coding for C++. One of them explored a feature called "Hardware exceptions" .Hard

Re: [Pharo-users] using UFFI in non-crashing way

2017-03-26 Thread Esteban Lorenzano
> On 26 Mar 2017, at 15:40, Peter Uhnak 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 no