scsh-users
[Top] [All Lists]

Re: revival of "Channel closed N N"

To: RT Happe <rthappe@mathematik.uni-freiburg.de>
Subject: Re: revival of "Channel closed N N"
From: Martin Gasbichler <gasbichl@informatik.uni-tuebingen.de>
Date: Tue, 03 Dec 2002 17:15:24 +0100
Cc: scsh <scsh@zurich.ai.mit.edu>
>>>>> "RT" == RT Happe <rthappe@mathematik.uni-freiburg.de> writes:

RT> On Tue, 3 Dec 2002, Martin Gasbichler wrote:
>> >>>>> "RT" == RT Happe <rthappe@mathematik.uni-freiburg.de> writes:
>> 
RT> By the way, I get sporadically messages like
schnada> ,load contempt.scm
RT> contempt.scm
RT> Channel closed: contempt.scm 6
>> 
RT> in scsh 0.6.2, which seem to suggest that the loader lets open ports hang
RT> around.
>> 
>> It would be nice to have a way to reproduce this.
>> 
>> I see these messages only when some time before an error occurred. Do
>> you even see them without errors?

RT> No, same for me, as it seems.  The reported occurence was the first I
RT> noticed since quite a few weeks, but I got some more in the rest of that
RT> session, and they always seem to follow reader failures, although not
RT> immediately.  But I cannot reproduce them either:  in particular, doing
RT> ,collect after a failed ,load doesn't force the message.

You have to leave the new level to release the pointer to the port:

> ,load ~/tmp/bar.scm
~/tmp/bar.scm
Error: end of file inside list -- unbalanced parentheses
       #{Input-port #{Input-channel "~/tmp/bar.scm"}}
1> ,collect
Before: 600430 words free in semispace
After:  984815 words free in semispace
1> ,reset

Top level
> ,collect
Channel closed: ~/tmp/bar.scm 3
Before: 975414 words free in semispace
After:  987665 words free in semispace

I think we will fix this in the reader for 0.6.3.

-- 
Martin

<Prev in Thread] Current Thread [Next in Thread>