On Sat, Nov 15, 2008 at 11:03 PM, Evan Teran <[EMAIL PROTECTED]> wrote: > I wouldn't call the 0x0f thing a bug. It is a byte oriented op which > only effects the LSB of the operand. So the disassembly is technically > correct IMO.
Just a personal comment here: as a "user", I usually expected consistent behavior between the tools I use. Having to mentally map between different formats/syntaxes just slows down my work. That said, Even though that specific "and esp, 0xf0" instruction would affect only the LSB as you says, visually it looks wrong because it should preserve the other bytes. In math, you usually does this by having all other bits set to 1. Then reading the instruction above, it would appear that the instruction is clearing all bits other than bit4-7, unless you check some opcode table to verify that is is a BYTE operation. Just my 0.02 cents. Regards, -- Anderson Lizardo _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
