Re: [gforth] missing file included, error message corrupted

[Anton Ertl]

On Sat, Aug 17, 2013 at 06:51:06PM +0200, Marcos Cruz wrote:
> Some time ago I realized a strange issue (Gforth 0.7.0 on Raspberry Pi's
> Raspbian) when a missing file is included.  I have just tried it with
> detail. When the command is given from the command line,
> 
>       include missing.fs
> 
> ...the error message is right. But if the same single command is in an
> included file,
> 
>       include exists.fs  \ <exists.fs> contains only 'include missing.fs'
> 
> ...then the failed source line in the error message is randomly
> corrupted (squares and other chars are shown instead of letters -- but
> the ">>>" and "<<<" marks are printed fine). The way the characters are
> corrupted don't make me think about a UTF-8 issue, but a mispointed
> string address.
> 
> The message is corrupted only the first time. If you try 'include
> exits.fs' more times, the error message is fine.

Thanks for the report.  I cannot reproduce this, neither on Debian 5.0
with Gforth built from source, nor with Ubuntu 12.04 and its Gforth
package:

[a4:/tmp:51781] echo "include missing.fs" >exists.fs
[a4:/tmp:51783] ~/nfstmp/xxxgforthtest/c8/gcc-3.4/install/bin/gforth-0.7.0     
Gforth 0.7.0, Copyright (C) 1995-2008 Free Software Foundation, Inc.
Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
Type `bye' to exit
include exists.fs 
exists.fs:1: No such file or directory
include >>>missing.fs<<<
Backtrace:
$7FFC0F2D8EA8 throw 
$7FFC0F2D8FC0 included 

If Bernd cannot reproduce this, this does not mean that the bug is
fixed.  I don't remember fixing it.  Do you, Bernd?

On which version of Debian are you getting this problem, and is it the
Debian build of Gforth or did you build it from source?  What version
of the distributions where it failed did you use?

- anton