[BUG]UndefinedObject(Object)>>doesNotUnderstand: #methodsFor:stamp:

Trying to install the package "ODBC for Squeak" with the SqueakMap
Package Loader in a clean 3.9g image end up in a DNU debugger.

26 September 2006 11:26:04 am

VM: Win32 - a SmalltalkImage
Image: Squeak3.9gamma [latest update: #7061]

SecurityManager state:
Restricted: false
FileAccess: true
SocketAccess: true
Working Dir C:\Program Files\Squeak 3.9
Trusted Dir C:\Program Files\Squeak 3.9\Lamneth Consulting
Untrusted Dir C:\My Squeak\Lamneth Consulting

UndefinedObject(Object)>>doesNotUnderstand: #methodsFor:stamp:
        Receiver: nil
        Arguments and temporary variables:
                aMessage: methodsFor: 'accessing' stamp: 'dgd 6/2/2002 00:33'
        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: 'ExternalStructure methodsFor: ''accessing'' stamp:
''dgd 6/2/200...etc...
                aContext: nil
                receiver: nil
                aRequestor: nil
                failBlock: [] in Compiler class>>evaluate:for:notifying:logged: {[^
nil]}
                logFlag: false
                methodNode: DoIt
        ^ ExternalStructure methodsFor: 'accessing' stamp: 'dgd 6/2/2...etc...
                method: a CompiledMethod (891)
                value: nil
        Receiver's instance variables:
                sourceStream: a ReadStream 'ExternalStructure methodsFor:
''accessing'' stamp: ...etc...
                requestor: nil
                class: UndefinedObject
                category: nil
                context: nil
                parserClass: Parser

Compiler class>>evaluate:for:notifying:logged:
        Receiver: Compiler
        Arguments and temporary variables:
                textOrString: 'ExternalStructure methodsFor: ''accessing'' stamp:
''dgd 6/2/200...etc...
                anObject: nil
                aController: nil
                logFlag: false
        Receiver's instance variables:
                superclass: Object
                methodDict: a
MethodDictionary(#compile:in:classified:notifying:ifFail:->a
Comp...etc...
                format: 142
                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: #'Compiler-Kernel'
                traitComposition: nil
                localSelectors: 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:
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:
[] in
SMDefaultInstaller(SMSimpleInstaller)>>fileIntoChangeSetNamed:fromStream
: {[global newChanges: changeSet.  stream fileInAnnouncing: 'Loading ' ,
newNam...]}
BlockContext>>ensure:
SMDefaultInstaller(SMSimpleInstaller)>>fileIntoChangeSetNamed:fromStream
:
SMDefaultInstaller>>fileIn
SMDefaultInstaller>>install
[] in SMLoader>>installPackageRelease: {[(SMInstaller forPackageRelease:
aRelease) install.  myRelease = self instal...]}
BlockContext>>ensure:
CursorWithMask(Cursor)>>showWhile:
[] in SMLoader>>installPackageRelease: {[Cursor wait   showWhile:
[(SMInstaller forPackageRelease: aRelease) install...]}
BlockContext>>on:do:
SMLoader>>installPackageRelease:
SMLoader>>installPackageRelease
SMLoader>>perform:orSendTo:
[] in MenuItemMorph>>invokeWithEvent: {[(selArgCount := selector
numArgs) = 0   ifTrue: [target perform: selector] ...]}
BlockContext>>ensure:
CursorWithMask(Cursor)>>showWhile:
...etc...

thats the same error like Petr Fischer reported on the beginner-list.
In short: Install the FFI-Package. After this load the ODBC-Package.
The ODBC-Package use the FFI-Package calling the ODBC-interface on your platform (Windows etc.)
You need also on windows the file SqueakFFIPrims.dll in your directorie where the vm is. For other
platforms I didn't know.

Hope this helps

Cheers,
 Frank

-------- Original Message --------
Subject: [BUG]UndefinedObject(Object)>>doesNotUnderstand: #methodsFor:stamp: (26-Sep-2006 17:29)
From:    [hidden email]
To:      [hidden email]

Just a quick thought...  I've been trying to get
up-to-date with Squeak (my last installed version was
3.7) and so far, most packages don't load for numerous
reasons.

A lot of them are not up to date or incompatible with
3.9, some omit to specify dependencies with other
packages, others miss methods that are no longer in
the image, etc.

I think it would be more than useful if we'd update
all packages to be compatible with 3.9 (or the next
release) and add some SUnit tests to those packages
that don't have any.  I would personally volunteer to
port/test a lot of the database-related packages.

How useful iis it to have a gazillion packages in
SqueakMap if most of them don't work with the current distribution?

-----------------
Benoit St-Jean
Yahoo! Messenger: bstjean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)

Hi!

Benoit St-Jean <[hidden email]> wrote:
> I think it would be more than useful if we'd update
> all packages to be compatible with 3.9 (or the next
> release) and add some SUnit tests to those packages
> that don't have any.  I would personally volunteer to
> port/test a lot of the database-related packages.

I will (but I was planning to do that anyway) try to get SM into a bit
of better shape (the server side cache is making more trouble than
helping right now) and of course port my packages like KomHttpServer
etc.

regards, Göran

Hi benoit

> How useful iis it to have a gazillion packages in
> SqueakMap if most of them don't work with the current distribution?

This is true.

Now did you ported some packages to 3.9?
Because of course we can complain but we can also contact the package  
maintainer
and mention to them that some of their packages work or not with the  
latest release.

I think that there is no simple consumer/producer pattern.

stef

Bien le bonjour monsieur Ducasse!

Non je n'ai pas encore porté de "package" sur 3.9.  De
ce que j'ai cru comprendre sur le "mailing list",
cette version a encore quelques petits problèmes.
Mais dès que j'ai une version 3.9 stable (ou 4.0), je
vais m'y mettre!

J'encourage tout le monde à essayer de "loader"
quelques "packages" dans une image vierge...  C'est
étonnant de voir à quel point plusieurs "packages"
sont "broken" (à moins que ce soit l'image de 3.9).

--- stephane ducasse <[hidden email]>
wrote:


-----------------
Benoit St-Jean
Yahoo! Messenger: bstjean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)

> Bien le bonjour monsieur Ducasse!
>
> Non je n'ai pas encore porté de "package" sur 3.9.  De
> ce que j'ai cru comprendre sur le "mailing list",
> cette version a encore quelques petits problèmes.
> Mais dès que j'ai une version 3.9 stable (ou 4.0), je
> vais m'y mettre!

3.9 is final!
And there is no problem that are stopping the release

> J'encourage tout le monde à essayer de "loader"
> quelques "packages" dans une image vierge...  C'est
> étonnant de voir à quel point plusieurs "packages"
> sont "broken" (à moins que ce soit l'image de 3.9).

It was easy. I hope that you feel better.
But the experience will show you that 3.9 is good.
Have a look at the number of fixes and changes we did.
Good night.

>

Oups!  Posted my reply in French...

Stéphane, I never implied that this release was s***.
I noticed the huge number of changes that went into
this release and good job to everyone.  BUT right now
a lot of packages don't load into 3.9.

I guess those packages will eventually get updated but
right now, this is very frustrating!

For instance, on my last attempt trying to install the
Chronos package creates a "Error occurred during
install: can't find EOCD position"...

--- stephane ducasse <[hidden email]>
wrote:


-----------------
Benoit St-Jean
Yahoo! Messenger: bstjean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)

Another point: look at the effort of the squeak-dev image.
Is it not great to see all the package maintainer pushing in the same  
direction?
I want to thanks them all for that.

        Yes it is cool so let us do it more often because this is the way  
that we will get
        a better system

So if you want to do something for the community, may be
paste all the packages on a wiki page and report the broken ones and  
try to notify the owners.

Stef

On 26 sept. 06, at 21:36, Benoit St-Jean wrote:

On 26 sept. 06, at 21:44, Benoit St-Jean wrote:

> Oups!  Posted my reply in French...
No problem I read french :)

>
> Stéphane, I never implied that this release was s***.
> I noticed the huge number of changes that went into
> this release and good job to everyone.  BUT right now
> a lot of packages don't load into 3.9.

sure.

> I guess those packages will eventually get updated but
> right now, this is very frustrating!

I imagine.

>
> For instance, on my last attempt trying to install the
> Chronos package creates a "Error occurred during
> install: can't find EOCD position"...

but I guess that this has nothing with the image but with the  
Squeakmap server
as far as I understood what goran said.

Hi!

Benoit St-Jean <[hidden email]> wrote:
That particular one sounds like SM server side cache gone wrong. Let me
try to fix that one right away....

...churn, churn, blonk, klonk... silence... Hmm? twirl, bang! bang!
Sigh...

Hmmm, ok, I think this was harder than I thought. It seems to me that
the stuff returned from that URL is this:

'<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=iso-8859-1">
<TITLE>chronos-st.org:80</TITLE>
</HEAD>
<FRAMESET
ROWS="130,*" FRAMEBORDER=0 BORDER=0 FRAMESPACING=0>
  <FRAME
NAME="content"
SRC="http://vhost.r4l.com/top_frm?domain=chronos-st.org:80"
marginheight=0 marginwidth=0 noresize scrolling=no>
  <FRAME
NAME="content"
SRC="http://apps5.oingo.com/apps/domainpark/domainpark.cgi?s=chronos-st.
org:80&cid=REGI991N&uid=62.181.231.43&dp_p4pid=oingo_inclusion_xml_10&dp
_lp=7&dp_pu=2&dp_format=1.3" marginheight=0 marginwidth=0 noresize>
 
<NOFRAMES>
    <META http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
    <META http-equiv="refresh" content="0;
url=chronos-st.org:80">
  </NOFRAMES>
</FRAMESET>
</HTML>
'

But using say wget or firefox I get the Chronos.sar file allright. Not
sure why this code does not work:

'http://chronos-st.org/downloads/Squeak/Chronos.sar' asUrl
retrieveContents contents

Anyone?

regards, Göran

Hi!

stephane ducasse <[hidden email]> wrote:
> > For instance, on my last attempt trying to install the
> > Chronos package creates a "Error occurred during
> > install: can't find EOCD position"...
>
> but I guess that this has nothing with the image but with the  
> Squeakmap server
> as far as I understood what goran said.

Right. What you can do to diagnose this situation is:

Open a transcript and try to download the specific release using "force
download into cache". If it starts blabbering like this:

Download from original url
(http://chronos-st.org/downloads/Squeak/Chronos.sar) failed with this
exception: Incorrect SHA checksum of file from orginal URL
Trying server cache instead.

...then the SHA1 checksum failed and it instead downloaded from the
server cache. Ok. Now, select the release and do "browse cache". Look at
the file content. If it, as in this case, clearly is not a sar file (a
sar file is a zip file) but rather HTML then tada - that will give you
the EOCD error (trying to unzip a non zip file).

regards, Göran

[hidden email] skrev: I reverted
HTTPSocket class httpGetDocument: url args: args accept: mimeType
request: requestString
to version tlk 1/22/2004 and I got the right content downloaded.
Karl

On 2006 September 26 15:45, stephane ducasse wrote:
Does putting a BUG report on Mantis such as "this error happens in 3.9
(details)" against a Squeak Package (e.g. RemoteFrameBuffer) produce email
the package maintainers? If it does not, it could be a useful addition, if it
does, perhaps we should be just reporting such 3.9 incompatibility on Mantis
(I added one earlier, I am not sure how to contact the maintainer)

Milan

On Tue, 2006-09-26 at 18:23 -0400, Milan Zimmermann wrote:
> Does putting a BUG report on Mantis such as "this error happens in 3.9
> (details)" against a Squeak Package (e.g. RemoteFrameBuffer) produce email
> the package maintainers? If it does not, it could be a useful addition, if it
> does, perhaps we should be just reporting such 3.9 incompatibility on Mantis
> (I added one earlier, I am not sure how to contact the maintainer)
>
> Milan

No it does not, and I don't think it is needed.  If you choose a
category, and that category is assigned to someone then that person will
get notice that an issue has been assigned to them.  Some of the
categories are currently assigned to people, many of them are not.
Perhaps in the future all of the categories should be assigned to
someone, perhaps the the release team leader by default; I wouldn't mind
discussing this with the new 3.10 release team.  In any case I really
don't think you should have to worry about an email being generated.  If
the release team can't be bothered to periodically check out Mantis for
new issues, after it has been around now for over 2 years, then either
it's time to find a new release team or it's time to just give up on
Mantis.

Ken

On 2006 September 26 18:41, Ken Causey wrote:
Ken,

Thanks, that make sense - so basically, each category has (or can have) a
responsible person, who does get a notice (is that an email?) when any issue
is assigned to that category, is that correct? If so, that is exactly what I
had in mind. I did not mean to say we should have a special treatment for
release-specific bugs such that "this package does has error in 3.9". My
wording was bad, I  actually ment to say everything should be reported and
handled like any other bug within Mantis (rather than use other mechanism),
just was not sure the reponsible person does get a notification.

Milan

> I wouldn't mind
> discussing this with the new 3.10 release team.  In any case I really
> don't think you should have to worry about an email being generated.  If
> the release team can't be bothered to periodically check out Mantis for
> new issues, after it has been around now for over 2 years, then either
> it's time to find a new release team or it's time to just give up on
> Mantis.
>
> Ken

What I found useful was the RSS feed because the UI of mantis does  
not work for me.
Sometimes I could spent 15 min trying to find something on this  
website (seriously this is
certainly my bad capacity with user interfaces but this was really  
annoying).

The problem is that I would love to have all the entries and their  
statuses in RSS.