forums.silverfrost.com

[wahorger]

Robert, yes, this is a side effect of memory being filled with spaces, incorrectly, wiping out local variables, and constants that would nominally be correct for error-free operation. The reason for this is mystifying especially since I did a test where none of my code was run, yet local variables did not have their set values (via a DATA statement).

I am no longer concerned about LENG8$, it is operating correctly if given correct inputs. In this case, it was not.

[mecej4]

Robert wrote: "It isn't byte 0x20 repeated, it is 0x02 repeated".

The index variable I_LOGMTR pertains to character*16 variables. The instructions

MOVSX_Q RBX,I_LOGMTR
IMUL_Q RBX,16_4

cause RBX to contain I_LOGMTR shifted left by one nybble, before the call to LENG8$, and the function does not touch RBX.

[Robert]

Ah, I see.