Squeak-dev November 2014

squeak-dev@lists.squeakfoundation.org

41 participants
125 discussions

Decompiler failure
by Tobias Pape 04 Nov '14

04 Nov '14

Hey all the following code fails to be decompiled by the Decompiler and I have no clue: retryOnce: aTryBlock | retry | retry := true. [[retry] whileTrue: [|result| result := aTryBlock value. retry := false. ^ result ]] on: Error do: [:e | retry := (e isKindOf: NetworkError) not ]. Apparently, the Decompilers stack is empty but it tries to access its last element, which results in an indexing error. Best -Tobias

4 4

flushCache
by Levente Uzonyi 03 Nov '14

03 Nov '14

Hi All, We have three primitives for three different versions of #flushCache: - primitive 89 used by Behavior >> #flushCache - primitive 116 used by CompiledMethod >> #flushCache - primitive 119 used by Symbol >> #flushCache Based on the comment in CompiledMethod >> #flushCache, and Symbol >> #flushCache, primitive 119 is not used since Squeak 2.3, and Symbol >> #flushCache can safely be removed. But the method is still in the image, and it is being sent whenever a method is removed or added to a class. Is the comment wrong, or the method is really not needed? Also the last comments in Behavior >> #basicAddSelector:withMethod: and Behavior >> #basicRemoveSelector: suggest that either the method's or the selector's cache should be flushed, but not both, which is actually the case in both methods. The comment in Symbol >> #flushCache suggests the same. So what's the truth? Do we still need primitive 119? Levente

3 5

New Cog VMs available
by Eliot Miranda 03 Nov '14

03 Nov '14

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3121/. CogVM binaries as per VMMaker.oscog-eem.918/r3121 This is for Spur: Fix bad bug in callPrimitiveBytecode. Old code skipped past next bytecode. This broke code depending on ContextPart>>restart, such as Exception>>retry. -- best, Eliot

2 1

Urgent: how to define a global?
by Chris Muller 01 Nov '14

01 Nov '14

Trying to debug a server, need to define a global OrderedCollection "X" which I want to put debugging objects into. In a workspace, I type: X := OrderedCollection new System asks me to correct or define a global. I choose to define a global. But I still cannot access X. It keeps asking me to correct or define a global. Yippee, great thing to happen at 4am when you just need to debug something! Digging in shows that when I try to access X, it ends up looking in Smalltalk environment 'bindings' IdentityDictionary, but when I defined X, it put the binding #X=>nil into Smalltalk environment 'declarations' only. I don't know what 'declarations' vs. 'bindings' are and I don't care, I just need to be able to define the global, could someone pelase tell me the proper fix? a) Defining X should put it in 'bindings' instead of 'declarations'? b) Accessing X should access from 'declarations' instead of 'bindings'? c) Defining X should put it in BOTH 'declarations' and 'bindings'?

7 11

Nw Cog VMs available
by Eliot Miranda 01 Nov '14

01 Nov '14

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3120/. These contain a few important bug fixes to Spur which will increase stability. CogVM binaries as per VMMaker.oscog-eem.916 Spur: Reimplement deriving the accessorDepth and retrying primitives on primitive failure machinery. Always take the primitive index from newMethod (setting newMethod to a SmallInteger for primitiveDoPrimitiveWithArgs. Have the Cogit always set primitiveFunctionPointer and newMethod for the retry. Add isNonInteger(Non)Immediate: and use it in several of the integer conversion routines that were missing code to exclude Character immediates, with fatal consequences. With these changes the Pharo 4 test suite runs without crashing on the latest Pharo Spur boot image. Fix processWeakSurvivor: so that it answers whether a weak object refers to a young object. The old version only scanned weak fields, ignoring refs to young objs from strong fields. Move check for valid classes from findClassOfMethod: forReceiver: into findClassContainingMethod:startingAt:, hence making findClassOfMethod:forReceiver: et al more robust. Implement safe access to contexts and methods when creating image segments (since internally married contexts and jitted methods have hidden state encoded in odd ways). As a result: Fix baaad bug in SpurMemoryManager>>lastPointerOf: for contexts, caused by transcription from (New)ObjectMemory where the method works on a wing and a prayer because BaseHeaderSize = BytesPerOop. And I can't be arsed to fix it. Fix baaad bug in accessibleObjectAfter: and add an assert to primitiveNextObject to catch similar bugs. Can now enumerate objects in new space, which will sort-of work, but code should really use allObjects. Will fix at the image level as time allows. Eliminate isInSurvivorSpace: in favour of the identical isInPastSpace:. All: Refactor decoding of context instruction pointers so there is only one copy of the code. -- best, Eliot

2 1