[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Full-Disclosure] Re: ndisasm bad opcodes interpretation
- To: full-disclosure@xxxxxxxxxxxxxxxx
- Subject: [Full-Disclosure] Re: ndisasm bad opcodes interpretation
- From: "Dave Korn" <davek_throwaway@xxxxxxxxxxx>
- Date: Fri, 7 Jan 2005 18:42:17 -0000
"shadown" <shadown@xxxxxxxxx> wrote in message
news:d8360fbf0501070830475ef080@xxxxxxxxxxxxxxxxx
>
> i.e:
> 0000001C 7565 jnz 0x83
> sould had been jnz 0x65
No it shouldn't. Engage brain before opening mouth: what is 0x65 + 0x1e
(== address of byte immediately after the instruction in question)? Google
"pc-relative branch displacement" for more. Or learn some assembler
programming before trying to use a disassembler.
cheers,
DaveK
--
Can't think of a witty .sigline today....
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html