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
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
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
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
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
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
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,
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