So, the only barrier to the user-level implementation is the problem
with instruction sizes. That's an enlightening point. Thanks for the
detailed answer!
Thanks everybody specially Steven and Mathieu.
Regards.
On 2020-07-16 02:18, Steven Rostedt wrote:
On Thu, 16 Jul 2020 02:09:50 +0430
ahm
Hi Steven and Mathieu,
Firstly, many thanks! This method seems to be the most efficient method.
But, IIUC, what you suggest requires source code compilation. I need an
efficient dynamic method that, given the function address, captures its
occurrence and stores some information from the executi
Hi Namhyung,
This seems really interesting and is what I am looking for. Can it
capture all function entries/exits? I mean does it fully handle variable
instruction sizes in dynamic mode?
In any case, thanks! and I hope that it becomes stable as soon as
possible, so that everyone can use it.
R
Hi Michel,
Thanks for the detailed answer! DBI tools are really interesting but
I want to do this during normal execution and on multiple programs
running simultaneously. I mean this is not supposed to
be conventional tracing with multiple re-executions. I want to
extract some information abou
Hi Frank,
Thanks for the point!
Regards.
On 2020-07-16 06:19, Frank Ch. Eigler wrote:
Hi -
If you can afford a more invasive tool, that requires a lot of
memory and stops your application for quite some time, you can look
at approaches like dyninst that decompile the binary, insert
instrum
Hi Michel,
Thanks for the detailed answer! DBI tools are really interesting but I
want to do this during normal execution and on multiple programs running
simultaneously. I mean this is not supposed to be conventional tracing
with multiple re-executions. I want to extract some information abou
