Ahh, that's why the code in CoInterpreter I was looking didn't match the C
code :D. Was looking at the wrong place, hehe.
Igor, why do you say that this method should be reached only with vanilla
compiled methods? From the comment I understand
For interpreter performance and to ease the
I'll make a summary from what I understand... Maybe we should move this
discussion to the VM list, but I'm not sure.
- Igor made changes to support the primitive 220
- those changes may try to activate a non-method object
- I added a check to tell if it is a compiled method or not to the new
It is fixed in latest vm (which you can get from the zeroconf script
http://get.pharo.org/vmLatest) :).
Guille
On Fri, May 31, 2013 at 1:25 PM, Igor Stasenko siguc...@gmail.com wrote:
On 31 May 2013 09:20, Guillermo Polito guillermopol...@gmail.com wrote:
Ahh, that's why the code in
I'll have to give this a try once I've upgraded my machine. I only
have GLIBC_2.11 and this requires GLIBC_2.15.
Excellent news though!
frank
On 31 May 2013 14:17, Guillermo Polito guillermopol...@gmail.com wrote:
It is fixed in latest vm (which you can get from the zeroconf script
Hi Frank,
I'm not able to reproduce this. I'm running Pharo.image and selecting
FileSystemHandleTest
FileHandleTest
FileSystemResolverTest
FileSystemTest
DiskFileSystemTest (Disc please!!)
MemoryFileSystemTest
On 30 May 2013 22:59, Eliot Miranda eliot.mira...@gmail.com wrote:
Hi Frank,
I'm not able to reproduce this. I'm running Pharo.image and selecting
FileSystemHandleTest
FileHandleTest
FileSystemResolverTest
FileSystemTest
