On 08-Nov-97 Ben Pfaff wrote: > Shaleh <[EMAIL PROTECTED]> writes: >> Barring malicious users, could these op codes have happened in >> production code? > > At least according to the gas 2.8.1 sources, the instruction code > 0x0f0f is not assigned to any instruction, so they should never appear > in actual code.
I can think of two ways it could have come about "innocently": a) Someone had a program which locked up (maybe tried to execute a Word (TM) doc file??). Localising the cause got it down to a few short segments of binary code. The programlet is a tidy way to isolate and test such things, and one of them did the trick. After which you warn your friends, and pass it on to your enemies. b) Someone wondered (as one does) what might possibly happen if you tried the unassigned codes. Thereafter as (a). Cheers, Ted. -------------------------------------------------------------------- E-Mail: Ted Harding <[EMAIL PROTECTED]> Date: 08-Nov-97 Time: 23:40:28 -------------------------------------------------------------------- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
