From: Sir Guenther <lists.guenther@googlemail.com>
To: 9fans@9fans.net
Subject: [9fans] acid. cormap vs. symmap
Date: Sun, 4 Apr 2010 20:10:38 +0000 [thread overview]
Message-ID: <j2v27f4bb321004041310ybe0655b9y74b158bbf3bd5d69@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Hey,
I am currently trying to debug a program, where the image map acid builds is
pretty much fubar. This obviously breaks a lot of stuff in acid. Still it
makes me wondering about some design decissions.
eg. asm from port.
It takes it's instructions from symmap. Why? I am interested at the
_current_ instructions?
Okay this is not really a problem...I just override asm and done.
However replacing @addr++ with *addr++ reveils another interesting thing.
The increment operation searches for the instruction length in the symmap by
default. Which obviously breaks again...
And I cannot override that from within acid itself.
Am I missing something obvious here?
Best regards,
Andre
[-- Attachment #2: Type: text/html, Size: 748 bytes --]
next reply other threads:[~2010-04-04 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 20:10 Sir Guenther [this message]
2010-04-04 20:55 ` erik quanstrom
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=j2v27f4bb321004041310ybe0655b9y74b158bbf3bd5d69@mail.gmail.com \
--to=lists.guenther@googlemail.com \
--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).