[DynInst_API:] Fwd: Dyninst callpath collection

[Jeff Hollingsworth <hollings@xxxxxxxxxx>]

Matt,

Could you answer this question?  I think it really boils down to a stack walker question.

Jeff


-------- Original Message --------

Subject:	[DynInst_API:] Dyninst callpath collection
Date:	Tue, 13 Aug 2013 22:51:11 -0700
From:	Milind Chabbi <Milind.Chabbi@xxxxxxxx>
To:	dyninst-api@xxxxxxxxxxx

I am considering using dyninst for a heavy-weight instrumentation
where I would like to monitor each memory access instruction.
In addition, on each monitored instruction I would like to store the
call path for a later use.
I noticed in the documentation that I can use getCallStack() API to
get the call stack.
I would like to know how getCallStack() works. Does it perform a call
stack unwind or does dyninst maintain a shadow call stack? I imagine
it is the former.
If it is unwinding based, perhaps calling getCallStack() very
frequently is expensive, is there any alternative?

-Milind
_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api