Bugs item #410467, was updated on 2001-03-21 21:41
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=410467&group_id=10493
Category: run-time
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Brian D. Carlstrom (bdc)
Assigned to: Olin Shivers (olin-shivers)
Summary: run/strings bug in 0.5
Initial Comment:
From: Pawel Turnau <uzturnau@cyf-kr.edu.pl>
To: scsh-bugs@martigny.ai.mit.edu
Subject: run/strings bug in 0.5
Date: Thu, 05 Nov 1998 16:55:00 +0100
I believe I may have uncovered a bug in scsh 0.5.
To reproduce it, create a file called bug-line with
just one line in
it:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxx\
x\263xx
It must have exactly 83 characters, and the third one
counting from
the end must be decimal ascii 179 (which, in ISO8859-
2, represents the
character l stroke). (I have tried some variations on
this -- like
moving the 179 character to other places, or changing
the length of the
string, but then the bug fails to manifest itself).
Now evaluate the following expression:
(run/strings (cat bug-line))
The interpreter (started with the command "scsh")
responds
'("xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxx\
xxxx" "xx")
in other words, it splits the single line into two
strings.
I have tried this on Solaris and on Linux.
Best regards,
Pawel Turnau
----------------------------------------------------------------------
>Comment By: Olin Shivers (olin-shivers)
Date: 2001-05-11 16:17
Message:
Logged In: YES
user_id=101304
This has been fixed, though I can't remember
what the problem was. Works on my linux box,
for sure.
-Olin
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=410467&group_id=10493
|