>A disassembler just uses a table. The intel documentation describes all >the instruction, with the method on how do decode it (not really the method >you have to write it of course). >A disassembler should know where to start to disassemble, else he will >start by disassembling bad data.. and probably fail on an unknown or >unlogical instruction, or the worst case everything will be ok. Thanks! What is the condition that decide one byte is or not a legal instruction's start ? Are there some occasions that disassembler need scan more than one byte to detect its logic ? -- To unsubscribe from this list: send the line "unsubscribe linux-assembly" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
- Follow-Ups:
- Re: Disassembly of 00000
- From: Sofiane Akermoun
- Re: Disassembly of 00000
- References:
- Disassembly of 00000
- From: horseriver
- Re: Disassembly of 00000
- From: Brian Raiter
- Re: Disassembly of 00000
- From: horseriver
- Disassembly of 00000
- Prev by Date: RE: Disassembly of 00000
- Next by Date: Re: Disassembly of 00000
- Previous by thread: Re: Disassembly of 00000
- Next by thread: Re: Disassembly of 00000
- Index(es):