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 all of the calling contexts that sampling reveals, and annotate each calling context with metrics (e.g., instructions executed, or cycles). If that doesnât meet your needs, return to your discussion in progress :-).
--
John Mellor-Crummey
Professor
Dept of Computer Science
Rice University
email: johnmc@xxxxxxxx phone: 713-348-5179
On Apr 23, 2018, at 4:55 PM, Buddhika Chamith Kahawitage Don <
budkahaw@xxxxxx> wrote:
Sorry for mixing up the emails. Earlier one was from my private email.
_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxxhttps://lists.cs.wisc.edu/mailman/listinfo/dyninst-api