Vm-dev May 2010

vm-dev@lists.squeakfoundation.org

22 participants
59 discussions

Handling exceptions during callback
by Igor Stasenko 04 May '10

04 May '10

Hello, Andreas and Eliot, i direct my question mainly to you , because you are most experienced in this area, but if there's others who want to share their thoughts, please do so. So, the question is, what to do, if an error triggered during a callback. My concern is, that sometimes its unsafe to do return from callback with invalid value. For example, if callback's caller expects a pointer to something, returning a default value (NULL) will have the same effect as simply terminating VM :) Here's my snippet of code, which i coded so far: block: aBlock self numberOfArguments = aBlock numArgs ifFalse: [ self error: 'Invalid number of arguments' ]. context := [ "here we entering a callback" [ [ | args | args := self readArguments. self leave: (aBlock valueWithArguments: args) ] ifCurtailed: [ self error: 'attempt to non-local return across a callback' ] ] repeat. ] asContext when callback is activated, an interpreter should enter the context , stored in callback's context ivar. The best what i invented so far, is to wrap the whole thing in repeat block. So, if there's error happens, there could be at least chance that user (like me ;) might supply the right argument to the #leave: method, using debugger. A leave: method serves to leave callback , but also might fail, if it can't coerce a return value to corresponding C equivalent. Of course, there's many other variants, like self leave: ( [ aBlock valueWithArguments: args ] ifCurtailed: [ self askUserToEnterTheValue ] ) i'd like to know, what you think would be the best variant. -- Best regards, Igor Stasenko AKA sig.

3 3

Question about memory allocation in VM
by Mariano Martinez Peck 04 May '10

04 May '10

Sorry in advance if this was asked before...I have something in my mind that says it was :( I want to know how the memory is allocated between the VM and the OS. For example, I know (actually, I think I know) that in Mac OS VM when you run an image, the VM allocates (malloc() I guess) the same size at least, of the image. So...I couple of questions: 1) Is the same behavior for all OS ? If not, which happens with the rest? 2) Where is such behavior defined? I don't think it is in VMMaker but in the C support code of each VM. But where (.c and function anme) , any quotes? 3) In am working (actually yet thinking) a mechanism that will probably use much less memory than the image. The idea is to swap to disk unused objects. Then....the amount of memory I will use should be MUCH smaller than the size of the image. So my question is, which changes should I do to the VM so that it uses only THAT amount of memory and not the size of the image. As I said, suppose I have an image size (in disk) on 15MB. Suppose I run that image, and then, as I swapped a lot of objects to disk, the actual usage of memory is 3 MBs. So what I want is that OS only uses 3 MB and not 15. Can I do that ? Thanks a lot for answering to this newbie :) Mariano

4 4

primFailCode currently dormant?
by Igor Stasenko 04 May '10

04 May '10

Hello, Alien adds a new primitive pragma: <primitive: 'foo' error: tempName module: 'bar' > where tempName is auto-declared during parsing as a special temp which will be used to retrieve primitive error code. i.e. myMethod <primitive: 'foo' error: code module: 'bar' > "prim failed , check the error code" code = 5 ifTrue: [ self error: 'you wrong' ] code = 666 ifTrue: [ self error: 'you are wrong as hell' ] The problem is, that i found that while its integrated in parser (through Alien package overrides), it leads to nowhere in current Interpreter. :( The sole reference to primFailCode is only in #primitiveFailFor: , which actually should be used by prims to set the failure code: Interpreter>>primitiveFailFor: reasonCode "Set specific primitive failure." primFailCode := reasonCode. self primitiveFail. I'd like to propose an alternative implementation: - at VM side , add only a single primitive: primitiveLastFailureCode self export: true. self pop: 1 thenPush: (self integerObjectOf: primFailCode). "reset the code" primFailCode := 0. At language side, we can support both, old and new format: Add the method , which will retrieve the code: Object>>lastFailureCode "Primitive: answer the last primitive failure code. Resets the failure code. Note: it can fail only if we're running on older VMs, which has no support of this primitive, if so, answer the generic failure code" <primitive: 'primitiveLastFailureCode' module: ''> ^ 0 And then, to handle things manually, one could use: Myclass>> foo <primitive: 'myprimitive' module: 'mymodule> "we're failed" | code | code := self lastFailureCode. ... handle the error code... And to support the Alien's new pragma pattern (primitive:error:module:) it can simply instruct the encoder to generate an implicit bytecode sequence (at method's beginning), which equals to: temp := self lastFailureCode. (where temp, is one, which used in pragma) What you think? -- Best regards, Igor Stasenko AKA sig.

3 7

Running Alien on Windows
by Torsten Bergmann 04 May '10

04 May '10

David wrote in [1] >I added Alien functions to VMMaker on SqueakSource: Thanks for the integration. So what is the next logical step to get Alien for Windows? Does it just mean Andreas has to build a new VM version? Thanks Torsten [1] http://lists.squeakfoundation.org/pipermail/vm-dev/2010-April/004382.html -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 4

Re: [squeak-dev] Obtaining a current context in primitive
by Eliot Miranda 03 May '10

03 May '10

Igor, surely if you're writing primitives that do context manipulation these should be internal to Interpreter, just like the block value and process/semaphore primitives. IMO its a really really bad idea to expose contexts through InterpreterProxy. (& redirecting to vm-dev) On Sat, May 1, 2010 at 7:32 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello guys, > > i am looking for a way, how i can obtain an activeContext oop in my > primitive function. > An activeContext variable is directly accessible for interpreter code, > but not for plugins. > So, i need some indirect way to retrieve it, to avoid patching the > Interpreter for exposing it. > > What i actually want is to switch an active context to a different > one, but remember a previously active, > so it can be restored later. > > -- > Best regards, > Igor Stasenko AKA sig. > >

2 1

Question about dragging an image into the vm in Windows
by Mariano Martinez Peck 02 May '10

02 May '10

Hi folks. It has been asked a problem in Pharo mailing list and I wanted to ask you. The summary is this: - You are allowed to take a .image and drag it into a vm (.exe) and this will run the VM with the dragged image - In such case, the image is interpreted as systemAttribute 1 The problem is when you define a image in the ini file. Suppose I add this to my ini file: ImageFile=Contents\Resources\Pharo-1.0.image Then, if I try to drag and drop another image to the VM, there will be an UTF8 input error as the thing that I dragged (the image) is interpreted as systemAttribute 2 and thus, in the method startUpAfterLogin it seems systemAttribute 2 is the sources file. So, it tries to load such file as if it were a text file, but as it is an image file...then the error. The ideal would be: if I have defined a image in the file, to be allowed to drag another one. Of course, the one I drag should be used and set as systemAttribute 1. Do you know how can I do that? is this fixable ? In other hand, maybe I can do a validation and a nice error message in case the above cannot be done. Thanks Mariano

4 6

Re: OSProcess reported crashing Mac VM (was: [squeak-dev] Squeak All-in-One)
by David T. Lewis 01 May '10

01 May '10

Thanks, this is very helpful. These tests are all using #primForkSqueak to run a headless background Squeak process. I think that this used to work on OS X, although I am not certain. As a workaround until this can be fixed, you can prevent the VM crash like this: UnixOSProcessAccessor>>primForkSqueak self primitiveFailed "broken on OS X" Dave On Sun, May 02, 2010 at 03:02:55AM +0900, NISHIHARA Satoshi wrote: > Hello > > The crashing primitives are: > UnixOSProcessAccessor>>#primForkSqueak > UnixOSProcessAccessor>>#primOldForkSqueak > > crashing methods are: > UnixProcessFileLockingTestCase > testCooperatingProcesses01 > testCooperatingProcesses02 > testCooperatingProcesses03 > testCooperatingProcesses04 > testCooperatingProcesses05 > testLockEntireFileForWrite01 > testLockEntireFileForWrite02 > testLockEntireFileForWrite03 > testLockEntireFileForWrite04 > testLockEntireFileForWrite05 > testLockEntireFileForWrite06 > testLockRegionForRead01 > testLockRegionForRead02 > testLockRegionForWrite01 > testLockRegionForWrite02 > testLockRegionForWrite03 > testLockRegionForWrite04 > testLockRegionForWrite05 > testLockRegionForWrite06 > testLockRegionForWrite07 > testLockRegionForWrite08 > > UnixProcessTestCase > testClassForkHeadlessSqueakAndDo > testClassForkHeadlessSqueakAndDoThenQuit > testClassForkSqueak > testClassForkSqueakAndDo > testClassForkSqueakAndDoThenQuit > testEightLeafSqueakTree > testHeadlessChild > testSpawnTenHeadlessChildren > testForkHeadlessSqueakAndDo > testForkHeadlessSqueakAndDoThenQuit > testForkSqueak > testForkSqueakAndDo > testForkSqueakAndDoThenQuit > > my environment is > muO All-in-One.app (app/Contents/Info.plist changed, only) > Mac OS X 10.5.8 (9L30) > MacBookPro5,1, Intel Core 2 Duo, 2.66 GHz > > regards. > > On 2010/05/02, at 00:15, David T. Lewis wrote: > > >On Fri, Apr 30, 2010 at 11:12:26PM +0900, NISHIHARA Satoshi wrote: > >>Hello > >> > >>muO-All-in-Onev2.zip, can't boot on my Mac. > >>Please change "SqueakImageName" key of app/Contents/Info.plist, to > >>correct image fine name: "Squeak3.8.2-6779+muO235.image" (not > >>include path). > >> > >>it can't to run all tests, because of vm crash. > >>2 testcases > >>UnixProcessFileLockingTestCase > >>UnixProcessTestCase > >>cause a VM crashing. > > > >Thank you very much for reporting the VM crash. > > > >I do not have a Mac to test this, but if anyone has further > >information on which primitive is crashing, I'd appreciate hearing > >further. Obviously save your image first ;-) > > > >Dave >

1 0

Problems with building a freetype plugin on linux
by Igor Stasenko 01 May '10

01 May '10

gcc -g -O2 -fomit-frame-pointer -DLSB_FIRST=1 -DHAVE_CONFIG_H -I/home/sig/squeak/src/build -I/home/sig/squeak/src/platforms/unix/vm -I/home/sig/squeak/src/platforms/Cross/vm -I/home/sig/squeak/src/src/vm -c /home/sig/squeak/src/src/plugins/FT2Plugin/FT2Plugin.c -fPIC -DPIC -DPIC -o FT2Plugin.o In file included from /home/sig/squeak/src/src/plugins/FT2Plugin/FT2Plugin.c:30: /usr/include/ft2build.h:56:38: error: freetype/config/ftheader.h: No such file or directory and ftheader.h contents says: /* `<prefix>/include/freetype2' must be in your current inclusion path */ #include <freetype/config/ftheader.h> So, it looks like a gcc flags missing the include option: -I/use/include/freetype2 -- Best regards, Igor Stasenko AKA sig.

4 10

OSProcess reported crashing Mac VM (was: [squeak-dev] Squeak All-in-One)
by David T. Lewis 01 May '10

01 May '10

On Fri, Apr 30, 2010 at 11:12:26PM +0900, NISHIHARA Satoshi wrote: > Hello > > muO-All-in-Onev2.zip, can't boot on my Mac. > Please change "SqueakImageName" key of app/Contents/Info.plist, to > correct image fine name: "Squeak3.8.2-6779+muO235.image" (not include path). > > it can't to run all tests, because of vm crash. > 2 testcases > UnixProcessFileLockingTestCase > UnixProcessTestCase > cause a VM crashing. Thank you very much for reporting the VM crash. I do not have a Mac to test this, but if anyone has further information on which primitive is crashing, I'd appreciate hearing further. Obviously save your image first ;-) Dave

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev May 2010