[Pharo-project] Bug in pharo image

Max Leske maxleske at gmail.com
Sun Jan 15 16:24:36 CET 2012

I see the problem but I wouldn't know who's responsible.

ConnectionQueue>>listeLoop contains the following line: 
newConnection := socket waitForConnectionFor: 10

"newConnection" is later sent the message #isConnected. The problem is that Socket>>waitForConnectionFor: answers "true" and not a connection object. IMHO this is definitely a bug. BTW, the issue on google code mentions a change by Levente that did chang #listenLoop but did *not* introduce the problem as far as I can see.

Thanks Garret for reporting. I think this should be fixed.


On 14.01.2012, at 22:34, Garret Raziel wrote:

> Hi, I think I found bug in pharo image. I would post it in bug tracker
> but I don't know if it is not duplicate to this bug
> http://code.google.com/p/pharo/issues/detail?id=3349&can=1&q=ConnectionQueue&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty.
> If you create ConnectionQueue to listen to some port, send it message
> "getConnectionOrNil" and there IS connection, debuger pops out with
> "MessageNotUnderstood True>>isConnected". I searched through code and
> obviously it is problem in ConnectionQueue>>listenLoop, that sends bad
> message to socket (Socket>>waitForConnection:), that returns true or
> false, not connection itself. It is works in squeak image.
> Should I post it to bugtracker? Or am I wrong? And isn't it duplicate
> to that link?
> Thanks,
> Jan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20120115/b5e1a302/attachment.htm>

More information about the Pharo-project mailing list