Mismatch between address offset in dalvik byte code and actual instruction trace

Hi I am running an application where the the Dex file instructions were having address or PC like 0x000253DC but when i get live instructions traces the PC or addresses are like 41ed7748 They are completely different in range.

I am just wondering is it normal or I am getting the traces wrong?

Thanks.

Answers


The addresses in native crash stack traces on Android appear as library offsets, so the high bits will be zeroed. Since the library location may change from run to run, the high part of the address is not included in stack traces.

See e.g. this question.

(None of which has anything to do with Dalvik bytecode, so I'm a little confused about the DEX file reference. Hopefully I'm not completely off base.)


Need Your Help

Twitter Bootstrap: Uncaught TypeError: Object modal1 has no method 'toggle'

javascript jquery html css twitter-bootstrap

I recently made a change to have some icons be the buttons that make a twitter-bootstrap modal appear on my site, and I am now getting the error:

Is it possible to prompt or force a user to upgrade their JVM with a JNLP?

java jnlp

I need to prompt users to upgrade from JVM 1.5 to 1.6 when they run my Web Start application. Is this possible using JNLP settings?