From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] acid. cormap vs. symmap
Date: Sun, 4 Apr 2010 16:55:15 -0400 [thread overview]
Message-ID: <1720fe559fc2273e7dcbaa798c6f5d7a@ladd.quanstro.net> (raw)
In-Reply-To: <j2v27f4bb321004041310ybe0655b9y74b158bbf3bd5d69@mail.gmail.com>
> However replacing @addr++ with *addr++ reveils another interesting thing.
> The increment operation searches for the instruction length in the symmap by
> default.
the symbol table has nothing to do with it. the behavior
of ++ depends on the type of addr. in your case, it has
type \I. \I interprets the (pointed-to) data as instructions.
compare:
acid /bin/cat
acid: x=read\I
acid: x++
SUBL $0x18,SP
acid: x++
INB DX,AL
acid: x++
SBBB CL,0x891c244c(BX)
acid: x++
ORB $0x24,AL
with
acid: x=read
acid: x++
0x000013a8
acid: x++
0x000013ac
acid: x++
0x000013b0
acid: x++
0x000013b4
- erik
next prev parent reply other threads:[~2010-04-04 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 20:10 Sir Guenther
2010-04-04 20:55 ` erik quanstrom [this message]
2010-04-04 21:03 ` Sir Guenther
2010-04-04 21:19 ` Sir Guenther
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=1720fe559fc2273e7dcbaa798c6f5d7a@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).