Re: [Pharo-dev] Reproducible VM Crash using UFFI

Yeh, the most important thing is what Jan says there. What you want to ensure is that you don't corrupt your memory (and particularly the heap). If you do so (i.e., corruption) the only way you can come back is that you remember the old uncorrupted value and, given that everything is still

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> So I think we are talking about different things here. I don't want > to > save "bad memory block" errors nor dream about bullet proof VM, but > if > we know the bullet then let's use a nice bulletproof vest :) > This can be done and has been done. Following code would clearly result in

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> On 8 Oct 2017, at 10:00, Hernán Morales Durand > wrote: > > Hi Esteban > > 2017-10-07 5:51 GMT-03:00 Esteban Lorenzano >: >> >> On 7 Oct 2017, at 00:11, Hernán Morales Durand >> wrote:

Re: [Pharo-dev] Reproducible VM Crash using UFFI

Hernan I imagine that valgrind in a "assembler interpreter." It does not blindly execute the next instructions. May be put trap everywhere and I do not think that we can do the same but I'm curious to read the answer about this one. On Sun, Oct 8, 2017 at 10:00 AM, Hernán Morales Durand

Re: [Pharo-dev] Reproducible VM Crash using UFFI

Hi Esteban 2017-10-07 5:51 GMT-03:00 Esteban Lorenzano : > > On 7 Oct 2017, at 00:11, Hernán Morales Durand > wrote: > > 2017-10-06 2:39 GMT-03:00 Sven Van Caekenberghe : > > > > On 6 Oct 2017, at 05:34, Hernán Morales Durand

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> On 7 Oct 2017, at 00:11, Hernán Morales Durand > wrote: > > 2017-10-06 2:39 GMT-03:00 Sven Van Caekenberghe >: >> >> >>> On 6 Oct 2017, at 05:34, Hernán Morales Durand >>> wrote: >>> >>> Hi Nicolas

Re: [Pharo-dev] Reproducible VM Crash using UFFI

2017-10-06 2:39 GMT-03:00 Sven Van Caekenberghe : > > >> On 6 Oct 2017, at 05:34, Hernán Morales Durand >> wrote: >> >> Hi Nicolas >> >> 2017-10-05 16:04 GMT-03:00 Nicolas Cellier >> : >>> >>> >>> 2017-10-05 15:42

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> On 6 Oct 2017, at 05:34, Hernán Morales Durand > wrote: > > Hi Nicolas > > 2017-10-05 16:04 GMT-03:00 Nicolas Cellier > : >> >> >> 2017-10-05 15:42 GMT+02:00 Hernán Morales Durand : >>> >>> I tried,

Re: [Pharo-dev] Reproducible VM Crash using UFFI

Hi Nicolas 2017-10-05 16:04 GMT-03:00 Nicolas Cellier : > > > 2017-10-05 15:42 GMT+02:00 Hernán Morales Durand : >> >> I tried, now I get an exception "Use ExternalAddress instead!" >> >> I guess the message means Use ExternalAddres in

Re: [Pharo-dev] Reproducible VM Crash using UFFI

2017-10-05 15:42 GMT+02:00 Hernán Morales Durand : > I tried, now I get an exception "Use ExternalAddress instead!" > > I guess the message means Use ExternalAddres in the "out" parameter. > But replacing byte with ExternalAddress also crashes the VM (crash.dmp >

Re: [Pharo-dev] Reproducible VM Crash using UFFI

then replacing "byte *” with ByteArray ? > On 5 Oct 2017, at 15:42, Hernán Morales Durand > wrote: > > I tried, now I get an exception "Use ExternalAddress instead!" > > I guess the message means Use ExternalAddres in the "out" parameter. > But replacing byte with

Re: [Pharo-dev] Reproducible VM Crash using UFFI

I tried, now I get an exception "Use ExternalAddress instead!" I guess the message means Use ExternalAddres in the "out" parameter. But replacing byte with ExternalAddress also crashes the VM (crash.dmp attached). 2017-10-05 10:03 GMT-03:00 Esteban Lorenzano : > >> On 5

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> On 5 Oct 2017, at 14:55, Hernán Morales Durand > wrote: > > Forgot to comment that Nacl worked in Pharo 5. yes but that was with NB and there are some minimum differences. I do not have the library and I lack the time to try more, but seems to me that here:

Re: [Pharo-dev] Reproducible VM Crash using UFFI

Forgot to comment that Nacl worked in Pharo 5. Cheers, Hernán 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano : > H Hernani, > > Most probably is a problem in the library and not UFFI, but I could not know > without a crash report. > > Esteban > >> On 5 Oct 2017, at 06:00,

Re: [Pharo-dev] Reproducible VM Crash using UFFI

Here it is. Let me know if you want to see the Linux crash report. Cheers, Hernán 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano : > H Hernani, > > Most probably is a problem in the library and not UFFI, but I could not know > without a crash report. > > Esteban > >> On 5

Re: [Pharo-dev] Reproducible VM Crash using UFFI

> On 5 Oct 2017, at 08:23, Esteban Lorenzano wrote: > > H Hernani, oops… Hernan… too early in the morning here ;) > Most probably is a problem in the library and not UFFI, but I could not know > without a crash report. > > Esteban > >> On 5 Oct 2017, at 06:00, Hernán

Re: [Pharo-dev] Reproducible VM Crash using UFFI

H Hernani, Most probably is a problem in the library and not UFFI, but I could not know without a crash report. Esteban > On 5 Oct 2017, at 06:00, Hernán Morales Durand > wrote: > > Hi, > > I ported Nacl (a libsodium wrapper) from the old FFI apicall: format > to

[Pharo-dev] Reproducible VM Crash using UFFI

Hi, I ported Nacl (a libsodium wrapper) from the old FFI apicall: format to use the UFFI ffiCall:, but there should be something terribly wrong because is crashing the VM, in both Windows 8.1 and Linux. How to reproduce in Pharo 6.1 Metacello new smalltalkhubUser: 'tonyg' project: