Hi, Thanks very much.
Regards Buddhika On Tue, Dec 5, 2017 at 9:33 AM, Xiaozhu Meng <xm...@cs.wisc.edu> wrote: > Hi, > > I find that I have source files for these examples. I will add them to the > repo. > > Buddhika: I will send them to you in a separate email. > > On Mon, Dec 4, 2017 at 8:02 PM, Buddhika Chamith Kahawitage Don < > budka...@umail.iu.edu> wrote: > >> Hi, >> >> Thanks for the pointers Thomas and Bill. Is there similar full source >> code example for the DataFlow API as well? I am specially interested in >> backward slicing for indirect jump target resolution example. >> >> Regards >> Buddhika >> >> On Mon, Dec 4, 2017 at 12:21 PM, Bill Williams <b...@cs.wisc.edu> wrote: >> >>> Also, the parseAPI example code exists as separate source files in >>> parseAPI/doc, and is incorporated into the manual at build time. It could >>> stand to get separated out as its own executable target, though. >>> >>> --bw >>> >>> ________________________________________ >>> From: Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of Thomas >>> Dullien <thomasdull...@google.com> >>> Sent: Monday, December 4, 2017 4:24 AM >>> To: Buddhika Chamith Kahawitage Don >>> Cc: Xiaozhu Meng; dyninst-api >>> Subject: Re: [DynInst_API:] Control Flow Graph example with parseAPI >>> >>> Hey there, >>> >>> not sure if this helps, but there is a fair bit of code that uses the >>> ParseAPI and CFGs here: >>> https://github.com/google/functionsimsearch >>> >>> In particular https://github.com/google/func >>> tionsimsearch/blob/master/dotgraphs.cpp dumps out >>> CFGs from an executable (ELF or PE) to .dot format for easy plotting. >>> >>> >>> Hope this helps, >>> Cheers, >>> Thomas >>> >>> On Mon, Dec 4, 2017 at 12:16 AM, Buddhika Chamith Kahawitage Don < >>> budka...@umail.iu.edu<mailto:budka...@umail.iu.edu>> wrote: >>> Sorry for the late response on this. Got side tracked with other >>> pursuits. Anyways it would be just easier if these examples were in the >>> form of executable tests/ examples within the Dyninst repository. Didn't >>> see something like that though. Did I miss it? (I laboriously copied stuff >>> from the pdf to assemble the example source. There is a chance I may have >>> missed some stuff during that process) >>> >>> Thanks >>> Buddhika >>> >>> On Mon, Nov 13, 2017 at 9:42 AM, Xiaozhu Meng <mxz...@gmail.com<mailto: >>> mxz...@gmail.com>> wrote: >>> Hi Buddhika, >>> >>> I have not encountered such issue before. If you still have this >>> problem, you can send me you source file and ELF binary, and I will try to >>> reproduce your issue and see what is happening. >>> >>> Thanks, >>> >>> --Xiaozhu >>> >>> On Fri, Nov 10, 2017 at 7:08 PM, Buddhika Chamith Kahawitage Don < >>> budka...@umail.iu.edu<mailto:budka...@umail.iu.edu>> wrote: >>> Hi All, >>> >>> I was trying to run control flow graph example (3.2) in the parseAPI >>> documentation. When I run on some ELF binary I am getting lot of non ascii >>> (binary) outputs instead of the intended output. Anyone come across this >>> before? >>> >>> Thanks >>> Buddhika >>> >>> _______________________________________________ >>> Dyninst-api mailing list >>> Dyninst-api@cs.wisc.edu<mailto:Dyninst-api@cs.wisc.edu> >>> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api >>> >>> >>> >>> _______________________________________________ >>> Dyninst-api mailing list >>> Dyninst-api@cs.wisc.edu<mailto:Dyninst-api@cs.wisc.edu> >>> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api >>> >>> >> >> _______________________________________________ >> Dyninst-api mailing list >> Dyninst-api@cs.wisc.edu >> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api >> > >
_______________________________________________ Dyninst-api mailing list Dyninst-api@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api