- May
- 592
- 4
In testing @BPOKE and @BPEEK to construct 32-bit integers like I described in another thread (it works, by the way), I mistyped and entered this:
C:\work> set bh=%@balloc[8]
C:\work> echo %@bpoke[%bh,8,1,0xfe]
0
The offset is out of bounds. No error condition was indicated.
Rex, it would be good if an out-of-bounds offset were flagged with a status code and ignored (i.e., not executed). Without a nonzero status code, it would still be okay if the deposited value (0xfe in this case) were NOT deposited anywhere.
Is this safe? Does it corrupt some part of process memory? (Of course I wouldn't do it on purpose -- but the offset could be a computed value and could go out of range.)
C:\work> set bh=%@balloc[8]
C:\work> echo %@bpoke[%bh,8,1,0xfe]
0
The offset is out of bounds. No error condition was indicated.
Rex, it would be good if an out-of-bounds offset were flagged with a status code and ignored (i.e., not executed). Without a nonzero status code, it would still be okay if the deposited value (0xfe in this case) were NOT deposited anywhere.
Is this safe? Does it corrupt some part of process memory? (Of course I wouldn't do it on purpose -- but the offset could be a computed value and could go out of range.)