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

Weird behavior of & function in Set

scala generics

Set is defined as Set[A]. It takes a in-variant parameter. Doing below works as expected as we are passing co-variant argument:

When isn't inlining safe?

optimization compiler-construction scope inline compiler-optimization

I keep reading (for example in the Closure Compiler and other compilers) that inlining of functions isn't always safe. Could you please provide an example when inlining of functions shouldn't be do...