Jim, one orthogonal follow-up question:
Is there a reason you're going image->module and then iterating over all
modules, rather than asking all of these questions at the image level?
And if you do that, does that fix the line information problem?
Rough pseudocode, omitting a ton of variable
On 10/01/2015 01:38 PM, Jim Galarowicz wrote:
Hi all,
I'm still not able to get source line information for use with the new
Dyninst 9.0.x loop interface change for finding the head node of the
loop in order to give the users the start line number for the loop.
That simple dyninst interface w
Hi all,
I'm still not able to get source line information for use with the new
Dyninst 9.0.x loop interface change for finding the head node of the
loop in order to give the users the start line number for the loop.
That simple dyninst interface was removed in 9.0.x.
I'm computing an address
Let me follow up on Bill's very complete and well phrased answer with a
comment more general than just Dyninst:
No static analysis tool can do a perfect job of finding basic blocks.
Just not possible.
And no dynamic tool can do a perfect job either, because there is no
guarantee that all th
On 10/01/2015 08:51 AM, chenping wrote:
Hello, Dyninst developers
I am using Dyninst to statically instrument the binary. Our work
heavily depends on the correctness of the basic block recognization.
So I would like to guarantee/know if there is any basic block cannot
be correctly reco
