|
From: | Paolo Bonzini |
Subject: | Re: [Help-smalltalk] Exception in the socket code |
Date: | Fri, 25 Mar 2011 14:59:21 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7 |
On 03/25/2011 02:43 PM, Holger Hans Peter Freyther wrote:
> Are you sure the problem isn't in the arguments to #nextAvailable:?Yes, besides an off by one in the source line the below causes the exception: count := count + available. Object: nil error: did not understand #+ MessageNotUnderstood(Exception)>>signal (ExcHandling.st:254) UndefinedObject(Object)>>doesNotUnderstand: #+ (SysExcept.st:1407) so I assume count is nil and this seems to be the case when the fileOp primitive is failing.
I mean, are you sure the primitive isn't failing because for example aCollection is bogus? I mean, this crashes the VM:
st> (FileDescriptor on: 0) nextAvailable: 1 into: 123 startingAt: 1 stdin:4: Aborted (ip 80)FileDescriptor>>#nextAvailable:into:startingAt: (ip 14)UndefinedObject>>#executeStatements (ip 0)<bottom> Aborted :) Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |