Re: [Gcl-devel] Seg fault in write-string.11

[Camm Maguire]

Greetings!  

What is happening here is that you are creating a stream loop, as
*standard-input* in GCL eval's to a synonym stream to *terminal-io*.

I was wondering whether this was a proper initial value for
*standard-input* and checked the spec -- apparently this arrangement is
specifically allowed.  The code below overruns the C stack as it
endlessly recurses trying to close *terminal-io*.  I suppose we could
put in some code to prevent such a recursion, but it is not obvious to
me at the moment where the comprehensive checking point for this would
be.  In any case, I suppose you are after the error 'cannot close
standard input'.  You can get this if you just rename your created two
way variable to anything else, e.g. *foo-io*.

Please let me know if this points out some serious GCL deficiency.

Take care,

"Paul F. Dietz" <address@hidden> writes:

> I'm trying to get the ansi-tests running again under gcl (with --enable-ansi).
> Test write-string.11 is segfaulting:
> 
>  >(with-output-to-string
>      (os)
>      (let ((*terminal-io* (make-two-way-stream *standard-input* os)))
>        (write-string "951" t)
>        (close *terminal-io*)))
> Segmentation fault
> 
>       Paul
> 
> 
> _______________________________________________
> Gcl-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gcl-devel
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah