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

[Bernd Paysan]

Am Samstag, 17. August 2013, 18:51:06 schrieb Marcos Cruz:
> Hi,
> 
> 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.

Yes, quite likely.

> The message is corrupted only the first time. If you try 'include
> exits.fs' more times, the error message is fine.
> 
> And finally, if <exists.fs> is included from the shell,
> 
>       gforth exists.fs
> 
> ...then the error message is always right.
> 
> 'require', 'required', 'include' and 'included' make no difference.
> 
> I have tried also two other platforms I have access at the moment:
> 
> - Gforth 0.6.2 on x86 (AMD K7) Debian works fine, though the error
>   messages are different in that version.
> 
> - Gforth 0.7.0 on x86 (Atom) Debian... exactly the same problem.
> 
> Is it a (known) bug?

Seems to be, as it has been fixed in the meantime.  Thanks for reporting.  I 
don't think we'll backport the fix to 0.7.x, because it is just annoying, but 
non-fatal.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/

signature.asc
Description: This is a digitally signed message part.