On Friday 22 November 2002 16:38, you wrote:
>
> Zoran,
>
> Here's a reproducible example of what I'm talking about:
>
> wats:nscp 75> encoding system
> iso8859-1
> wats:nscp 76> set u 아트미디어
> 아트미디어
> wats:nscp 77> set u
> 아트미디어
> wats:nscp 78> regexp {^(.*)$} $u junk m
> 1
> wats:nscp 79> set m
> 쩐횈트쨔絹챨쩐챤
>
> See how $m isn't the same as $u?
>
Using my encoding-aware nscp:
lexxsrv:nscp 1> set u 아트미디어
아트미디어
lexxsrv:nscp 2> set u
아트미디어
lexxsrv:nscp 3> regexp {^(.*)$} $u junk m
1
lexxsrv:nscp 4> set m
아트미디어
$m is the same as $u
>
> Any idea what I'm doing wrong?
As already posted to the list: the nscp trashes encoding.
But, the initial question was about the memory corruption
wasn't it? Somehow you got complaints from the memory
allocator which I'm not able to reproduce. Now, what was
the corrective measure again? It did have to do something
with nsv_* arrays, did it?
Cheers
Zoran
