| Date: | Fri, 10 Mar 2017 09:24:39 -0600 |
|---|---|
| From: | Xiaozhu Meng <xmeng@xxxxxxxxxxx> |
| Subject: | Re: [DynInst_API:] Static Taint Analysis using Dyninst |
|
Hi Sazzadur, It is suspicious that the absloc in your case was reported as a heap variable. It is clearly a stack variable. When the absloc is classified as a heap variable, slicing will have difficult time to match it with other heap variables statically because we do no necessarily know the exact address. I currently do not know why this simple stack access is reported as a heap access. I believe once we figure this issue out, the forward slicing issue should be resolved. I will get to you later when I have some more information. Thanks, --Xiaozhu On Thu, Mar 9, 2017 at 5:53 PM, Sazzadur Rahaman <sazzad14@xxxxxx> wrote:
|
| [← Prev in Thread] | Current Thread | [Next in Thread→] |
|---|---|---|
| ||
| Previous by Date: | [DynInst_API:] Static Taint Analysis using Dyninst, Sazzadur Rahaman |
|---|---|
| Next by Date: | Re: [DynInst_API:] Static Taint Analysis using Dyninst, Xiaozhu Meng |
| Previous by Thread: | [DynInst_API:] Static Taint Analysis using Dyninst, Sazzadur Rahaman |
| Next by Thread: | Re: [DynInst_API:] Static Taint Analysis using Dyninst, Xiaozhu Meng |
| Indexes: | [Date] [Thread] |