Re: [DynInst_API:] Problem in pointer alias analysis by using Dyninst

[Tim Haines <thaines@xxxxxxxxxxx>]

    The general problem with pointer aliasing is that there are many
    different sources of memory and each presents its own challenge-
    particularly heap memory. This isn't my area of expertise, but I
    believe using dataflow analysis would be a place to start.
    DataflowAPI won't have a single method to solve pointer aliasing
    because it's too complex of a problem, but the information it
    provides should get you started. Feel free to ask more questions
    here or open a question issue on our Github.
    
    Thanks.
    - Tim

On 12/12/22 3:37 PM, Wen Zhang wrote:

Dear developers,

I am using Dyninst to do the static binary analysis on x86/64. And I meet one problem with how to use Dyninst to identify two memory locations represented by different registers that may point to the same memory location. For example, there are two assembly codes: 

mov %rax, 0x8(%rbp)

mov %rcx, 0x4(%rcx)

Even though these two memory writings look totally different, 0x8(%rbp) and 0x4(%rcx) may point to the same memory location. 

I have looked at all manuals in Dyininst, but it seems nothing related to this problem. Is there any API or method given by Dyninst that can solve this problem?

I appreciate your feedback. 

Sincerely,

Wen Zhang

_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api