From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Date: Sun,  4 Apr 2010 20:10:38 +0000
Message-ID: <j2v27f4bb321004041310ybe0655b9y74b158bbf3bd5d69@mail.gmail.com>
From: Sir Guenther <lists.guenther@googlemail.com>
To: 9fans@9fans.net
Content-Type: multipart/alternative; boundary=0016e6d6454461751904836ecea3
Subject: [9fans] acid. cormap vs. symmap
Topicbox-Message-UUID: fc42778e-ead5-11e9-9d60-3106f5b1d025

--0016e6d6454461751904836ecea3
Content-Type: text/plain; charset=ISO-8859-1

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

--0016e6d6454461751904836ecea3
Content-Type: text/html; charset=ISO-8859-1

Hey,<br><br>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.<br><br>eg. asm from port.<br>
It takes it&#39;s instructions from symmap. Why? I am interested at the _current_ instructions?<br>Okay this is not really a problem...I just override asm and done.<br><br>However replacing @addr++ with *addr++ reveils another interesting thing.<br>
The increment operation searches for the instruction length in the symmap by default. Which obviously breaks again...<br>And I cannot override that from within acid itself.<br><br>Am I missing something obvious here?<br><br>
Best regards,<br>Andre<br>

--0016e6d6454461751904836ecea3--