public inbox for linux-assembly@vger.kernel.org
 help / color / mirror / Atom feed
From: horseriver <horserivers@gmail.com>
To: linux-assembly@vger.kernel.org
Subject: Re: Disassembly  of  00000
Date: Sun, 3 Feb 2013 02:54:40 +0800	[thread overview]
Message-ID: <20130202185440.GA2519@debian.localdomain> (raw)
In-Reply-To: <20749.23788.343335.87280@eidolon.muppetlabs.com>

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 majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-02-02 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02  4:53 Disassembly of 00000 horseriver
2013-02-02 18:37 ` Brian Raiter
2013-02-02 18:54   ` horseriver [this message]
2013-02-03  5:44     ` Sofiane Akermoun
     [not found]     ` <CAN0_x-Kw9TxbD4EHmD1Ns5BJtBXToW_qsXSZWRzEtKxObXMhSQ@mail.gmail.com>
2013-02-04  6:24       ` horseriver
2013-02-04 19:25         ` Sofiane Akermoun
     [not found]           ` <CADtGFvnaEgacU-FvtZZnOxkX4tbFxj6tYhqb-1ok6jwrMm=39Q@mail.gmail.com>
2013-02-04 22:54             ` Hendrik Visage
2013-02-03 16:42 ` Robert Plantz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130202185440.GA2519@debian.localdomain \
    --to=horserivers@gmail.com \
    --cc=linux-assembly@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox