Date: | Mon, 23 Apr 2018 21:20:09 +0000 (UTC) |
---|---|
From: | budchan chao <cbudchan@xxxxxxxxx> |
Subject: | 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 <mxz297@xxxxxxxxx> wrote:
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 collecting return addresses and manually reconstruct call stacks. If it is the case, the stackwalkAPI is better suited for this purpose. You can refer the documentation for better idea of what stackwalkAPI can do (https://github.com/mxz297/dyninst/blob/master/stackwalk/doc/stackwalk.pdf). Thanks, --Xiaozhu On Sun, Apr 22, 2018 at 2:49 PM, budchan chao <cbudchan@xxxxxxxxx> wrote:
|
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [DynInst_API:] new-parallel-parsing config is broken for testsuite, Mark W. Krentel |
---|---|
Next by Date: | Re: [DynInst_API:] new-parallel-parsing config is broken for testsuite, Xiaozhu Meng |
Previous by Thread: | Re: [DynInst_API:] Logging the stack trace, Xiaozhu Meng |
Next by Thread: | Re: [DynInst_API:] Logging the stack trace, Xiaozhu Meng |
Indexes: | [Date] [Thread] |