[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-smalltalk] Re: Exception in the socket code

From: Holger Hans Peter Freyther
Subject: Re: [Help-smalltalk] Re: Exception in the socket code
Date: Fri, 25 Mar 2011 20:29:38 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b2 Thunderbird/3.1.9

On 03/25/2011 03:33 PM, Paolo Bonzini wrote:
> On 03/25/2011 03:28 PM, Holger Hans Peter Freyther wrote:
>>> >
>>> >  I'll apply the part since it's good anyway.
>> hmm. does this mean I can't read data out of a remotely closed socket? Or 
>> only
>> when I have called close myself. Sorry for the stupid question.
> No, only when you have called close yourself.  In fact, I'm not sure what
> would call #close on the buffers; nothing, probably.  But the patch would
> definitely tell us if that's happening.
> Now that I think of it, while my patch to the buffer classes is good for GST,
> you may want to replace the two implementations of #close with just "self 
> halt".


I can reproduce the issue using tcpkill of dsniff on the connection. I will
debug tomorrow morning. While testing I think I stumbled across mem corruption
of DoIt's (Eval [] in a file) and doing CTRL+C (e.g. when waiting for a
socket...). It is causing a segfault when clearing the obstack. :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]