Re: Disassembly of 00000
horseriver <[email protected]> Sun, 3 Feb 2013 02:54:40 +0800
| Newsgroups | org.kernel.vger.linux-assembly |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Feb 02, 2013 at 10:37:32AM -0800, Brian Raiter wrote: > > I have a question about disassemblly utility . > > If I fill an elf's text section with some random data,then > > how does the disas command work for these data? > > Is there occasion that several sequence of bytes can not be translated > > into legal instructions? > > Yes, definitely. In those cases a typical disassembler will just mark > the first byte as being literally emitted and try to resume > disassembly at the next byte. For example, using ndisasm v2.07: Thanks! What is "literally emitted" meaning here? I guess you mean a const value definition. How does disassembler check the number of bytes which consist an instruction ? Can only noe byte tell the instruction's length? > > $ echo -e '\017zz' | ndisasm - > 00000000 0F db 0x0f > 00000001 7A7A jpe 0x7d > 00000003 0A db 0x0a > > b > -- > To unsubscribe from this list: send the line "unsubscribe linux-assembly" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html