About the #logChange error in SqueakMap

> Germán Arduino a écrit :
> > As neither responded, I'm attaching a .cs that solves the problem.
>
> I can't file-in your .cs. I'm running a 3.9a-7015, opened the 'file
> list' tool and try to filein the file. I get the following :
>
> UndefinedObject(Object)>>doesNotUnderstand: #methodsFor:stamp:
>         Receiver: nil
>         Arguments and temporary variables:
>                 aMessage:       methodsFor: 'installation' stamp: 'gsa 3/15/2006 11:20'
>         Receiver's instance variables:
> nil
>
> UndefinedObject>>DoIt
>         Receiver: nil
>         Arguments and temporary variables:
>
>         Receiver's instance variables:
> nil
>
> Compiler>>evaluate:in:to:notifying:ifFail:logged:
>         Receiver: a Compiler
>         Arguments and temporary variables:
>                 textOrStream:   'SMInstallationRegistry methodsFor: ''installation''
> stamp: ''gsa...etc...
>                 aContext:       nil
>                 receiver:       nil
>                 aRequestor:     nil
>                 failBlock:      [] in Compiler class>>evaluate:for:notifying:logged: {[^ nil]}
>                 logFlag:        false
>                 methodNode:     DoIt
>         ^ SMInstallationRegistry methodsFor: 'installation' stamp: 'g...etc...
>                 method:         a CompiledMethod (2342)
>                 value:  nil
>         Receiver's instance variables:
>                 sourceStream:   a ReadStream 'SMInstallationRegistry methodsFor:
> ''installation''...etc...
>                 requestor:      nil
>                 class:  UndefinedObject
>                 category:       nil
>                 context:        nil
>                 parserClass:    Parser
>
> Compiler class>>evaluate:for:notifying:logged:
>         Receiver: Compiler
>         Arguments and temporary variables:
>                 textOrString:   'SMInstallationRegistry methodsFor: ''installation''
> stamp: ''gsa...etc...
>                 anObject:       nil
>                 aController:    nil
>                 logFlag:        false
>         Receiver's instance variables:
>                 superclass:     Object
>                 methodDict:     a
> MethodDictionary(#compileNoPattern:in:context:notifying:ifFail:->...etc...
>                 format:         142
>                 traitComposition:       {}
>                 localSelectors:         nil
>                 instanceVariables:      #('sourceStream' 'requestor' 'class' 'category'
> 'context' 'p...etc...
>                 organization:   ('error handling' notify: notify:at:)
> ('public access' compile:in...etc...
>                 subclasses:     nil
>                 name:   #Compiler
>                 classPool:      a Dictionary()
>                 sharedPools:    nil
>                 environment:    a SystemDictionary(lots of globals)
>                 category:       nil
>
>
> --- The full stack ---
> UndefinedObject(Object)>>doesNotUnderstand: #methodsFor:stamp:
> UndefinedObject>>DoIt
> Compiler>>evaluate:in:to:notifying:ifFail:logged:
> Compiler class>>evaluate:for:notifying:logged:
>  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Compiler class>>evaluate:for:logged:
> Compiler class>>evaluate:logged:
> [] in MultiByteFileStream(PositionableStream)>>fileInAnnouncing: {[val
> := (self peekFor: $!)     ifTrue: [(Compiler evaluate: self nextChunk l...]}
> BlockContext>>on:do:
> [] in MultiByteFileStream(PositionableStream)>>fileInAnnouncing: {[:bar
> |  [self atEnd]   whileFalse: [bar value: self position.    self skipS...]}
> [] in ProgressInitiationException>>defaultMorphicAction {[result :=
> workBlock value: progress]}
> BlockContext>>ensure:
> ProgressInitiationException>>defaultMorphicAction
> ProgressInitiationException>>defaultAction
> UndefinedObject>>handleSignal:
> MethodContext(ContextPart)>>handleSignal:
> ProgressInitiationException(Exception)>>signal
> ProgressInitiationException>>display:at:from:to:during:
> ProgressInitiationException class>>display:at:from:to:during:
> ByteString(String)>>displayProgressAt:from:to:during:
> MultiByteFileStream(PositionableStream)>>fileInAnnouncing:
> MultiByteFileStream(FileStream)>>fileIn
> MultiByteFileStream>>fileIn
> FileStream class>>fileIn:
> SimpleServiceEntry>>performServiceFor:
> PluggableButtonMorph>>performAction
> [] in PluggableButtonMorph>>mouseUp: {[:m | (m containsPoint: evt
> cursorPoint)   ifTrue: [m performAction]]}
> Array(SequenceableCollection)>>do:
> PluggableButtonMorph>>mouseUp:
> PluggableButtonMorph(Morph)>>handleMouseUp:
> MouseButtonEvent>>sentTo:
> PluggableButtonMorph(Morph)>>handleEvent:
> PluggableButtonMorph(Morph)>>handleFocusEvent:
> [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self.
> ActiveEvent := anEvent.  result := focusHolder     han...]}
> [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]}
> BlockContext>>on:do:
> PasteUpMorph>>becomeActiveDuring:
> HandMorph>>sendFocusEvent:to:clear:
> HandMorph>>sendEvent:focus:clear:
> HandMorph>>sendMouseEvent:
> HandMorph>>handleEvent:
> HandMorph>>processEvents
> [] in WorldState>>doOneCycleNowFor: {[:h |  ActiveHand := h.  h
> processEvents.  capturingGesture := capturingGest...]}
> ...etc...
>
>
> --
> Damien Cassou
>
>
>

> Hi,
>
> thank you very much for your help, it works now.
>
> > 1) Start the SM upgrading.
> > 2) When you get the DNU error, start the debugger and go to the wrong
> > method and replace Smalltalk logChange by SmalltalkImage current
> > logChange.
> > 3) Hit Proceed and is done.
>
>
> Bye
>
>

> 2006/3/29, Damien Cassou <[hidden email]>:
>> Hi,
>>
>> thank you very much for your help, it works now.
>>
>>> 1) Start the SM upgrading.
>>> 2) When you get the DNU error, start the debugger and go to the  
>>> wrong
>>> method and replace Smalltalk logChange by SmalltalkImage current
>>> logChange.
>>> 3) Hit Proceed and is done.
>>
>>
>> Bye
>>
>>
>
> Not problem.
>
> I regrett really that this is a long time reported (and assigned) bug
> in Mantis. from February 18, very simple to solve, but seems that the
> maintainer of the package has no time :(

> It's a one line fix, but that has to be done in a repository where  
> I have no access
> to, so I can not fix it myself.... sorry. There is a downside of  
> "maintained" packages:
> Nothing happens with Network for 3 Months, we have not seen a Unix  
> vm build since
> three years, and SqueakMap is broken for 3 Months. Maybe we need to  
> define more
> clearly what it really means to be a Maintainer. Right now I have  
> the feeling that
> making something "maintained" is the best way to ensure that  
> nothing happns at all.

>
> On 30 mars 06, at 13:48, Marcus Denker wrote:
>
> > It's a one line fix, but that has to be done in a repository where
> > I have no access
> > to, so I can not fix it myself.... sorry. There is a downside of
> > "maintained" packages:
> > Nothing happens with Network for 3 Months, we have not seen a Unix
> > vm build since
> > three years, and SqueakMap is broken for 3 Months. Maybe we need to
> > define more
> > clearly what it really means to be a Maintainer. Right now I have
> > the feeling that
> > making something "maintained" is the best way to ensure that
> > nothing happns at all.
>
> Yes we should fix that.
>
> Stef
>
>

>
>> and SqueakMap is broken for 3 Months.
>
> "broken" is a bit harsh - yes, it flunks in the current 3.9alpha or
> beta, but not in 3.8 AFAIK.
>
> Now, if/when you fix it btw - make sure that the "SqueakMap" package
> (the script) picks the correct release of base and also - check that
> your fix works back in 3.6, 3.7 and 3.8 too.
>

> On 30.03.2006, at 14:53, [hidden email] wrote:
> >> and SqueakMap is broken for 3 Months.
> >
> > "broken" is a bit harsh - yes, it flunks in the current 3.9alpha or
> > beta, but not in 3.8 AFAIK.
> >
> > Now, if/when you fix it btw - make sure that the "SqueakMap" package
> > (the script) picks the correct release of base and also - check that
> > your fix works back in 3.6, 3.7 and 3.8 too.
> >
>
> Is this reasonable? One codebase for all Squeak versions? I mean, this

> Now apparently you want to help me and great, I am adding you as a
> co-maintainer and will send you write access to the server.
>
>> There is a downside of
>> "maintained" packages:
>> Nothing happens with Network for 3 Months,
>
> Things did happen a bit (at least *I* did a few fixes) but I didn't  
> get
> around to "zipping it all up". I think I explained it in detail if
> someone wanted to do the picking - but if noone does then I will
> eventually get around to it.

>> we have not seen a Unix vm
>> build since
>> three years,
>
> That is true and a bit worrying. Do we have any suggestions on who to
> pick that up? I can picture a few names in my head - but have no idea
> about interest.
>
>> and SqueakMap is broken for 3 Months.
>
> "broken" is a bit harsh - yes, it flunks in the current 3.9alpha or
> beta, but not in 3.8 AFAIK.

> Is this reasonable? One codebase for all Squeak versions? I mean, this
> would imply to add code that tests if the deprecated method has been
> removed or not, or it would not to test for the version (if version  
> X, call method
> Y, else method Z). This is bound to become very messy over time...
>
> Wouldn't it make more sense to freeze the external packages with  
> the release
> (to be developed much more cautiously) while forking a new unstable  
> branch
> for the new unstabe Squeak release?

> Marcus Denker wrote:
>> we have not seen a Unix vm build since three years,
>
> http://squeakvm.org/unix/release/
>
> Squeak-3.8a-1.noarch.rpm                         22-Mar-2005 14:11  
> 1.5K
> Squeak-3.8a-1.src.tar.gz                         22-Mar-2005 14:11  
> 2.4M
> Squeak-3.8g-6548.image.tar.gz                    22-Mar-2005  
> 14:11   11M
>
> That's about ten months old, and it's built for 3.8.

> Marcus Denker wrote:
>> we have not seen a Unix vm build since three years,
>
> http://squeakvm.org/unix/release/
>
> Squeak-3.8a-1.noarch.rpm                         22-Mar-2005 14:11  
> 1.5K
> Squeak-3.8a-1.src.tar.gz                         22-Mar-2005 14:11  
> 2.4M
> Squeak-3.8g-6548.image.tar.gz                    22-Mar-2005  
> 14:11   11M
>
> That's about ten months old, and it's built for 3.8.