Re: [DynInst_API:] Logging the stack trace

One more heretical suggestion for the Dyninst mailing list: you might be interested in the paper and download of software developed by some of my students for use with Pin. Milind Chabbi, Xu Liu, and John Mellor-Crummey. 2014. Call Paths for Pin Tools. In Proceedings of Annual IEEE/ACM

Re: [DynInst_API:] Logging the stack trace

Hi John, Looks like it's sampling based. For my current requirement I want full trace of the running stack at each call chain. Thanks for the suggestion though :). I've heard of it before. Looks like a pretty useful project. On Mon, Apr 23, 2018 at 6:19 PM, John Mellor-Crummey

Re: [DynInst_API:] new-parallel-parsing config is broken for testsuite

I see. I guess nobody told me. Sorry, Thanks, --Mark On 04/23/18 16:33, Xiaozhu Meng wrote: For parallel parsing branch, testsuite is now a submodule. So, please do git submodule init git submodule update ___ Dyninst-api mailing list

Re: [DynInst_API:] Logging the stack trace

Buddhika, Rather than using dyninst to collect every unique calling context that arises while executing a program using unwinding, you might find it appropriate to use HPCToolkit (http://hpctoolkit.org), which can measure your executing program using sampling + call stack unwinding, show you

Re: [DynInst_API:] Logging the stack trace

Sorry for mixing up the emails. Earlier one was from my private email. On Mon, Apr 23, 2018 at 5:49 PM, Buddhika Chamith Kahawitage Don < budka...@iu.edu> wrote: > I want to collect all the stack traces. This is for a study of spec > applications. > > On Mon, Apr 23, 2018 at 5:40 PM, Xiaozhu

Re: [DynInst_API:] Logging the stack trace

I want to collect all the stack traces. This is for a study of spec applications. On Mon, Apr 23, 2018 at 5:40 PM, Xiaozhu Meng wrote: > Do you want to collect all stack traces during its run or you have a few > points you are interested in where you want to collect stack

Re: [DynInst_API:] Logging the stack trace

Do you want to collect all stack traces during its run or you have a few points you are interested in where you want to collect stack traces (such as function entries, basic block entries)? On Mon, Apr 23, 2018 at 4:20 PM, budchan chao wrote: > Right, I want to just collect

Re: [DynInst_API:] Logging the stack trace

Right, I want to just collect all the return addresses and get all the stack traces a program makes during its run. So would work if I add this stack walking code as part of return instrumentation? On Monday, 23 April, 2018, 4:50:44 PM GMT-4, Xiaozhu Meng wrote: Hi,

[DynInst_API:] new-parallel-parsing config is broken for testsuite

The new-parallel-parsing branch of dyninst has this in the top-level CMakeLists.txt. add_subdirectory(testsuite) But the testsuite directory is empty in the n-p-p branch. As a result, cmake falls over with: -- Found dependency location /home/krentel/config/build-dyninst/dyninstAPI CMake Error

Re: [DynInst_API:] Logging the stack trace

Hi, Passing (rsp) to your instrumentation function is not going to do what you plan to do because Dyninst's internal instrumentation code will have changed the value of rsp. For us to better help you, can you describe what exactly you would like to do? It seems to me that you are trying to

[DynInst_API:] Research staff positions open at UW-Madison (Dyninst related)

The Paradyn project at the University of Wisconsin-Madison is looking for one (and possibly two) staff Researchers to work on our binary code analysis and instrumentation instrumentation project. The position is centered around our Dyninst suite of tools. We continue to push the frontiers of cool