Hi Josef,
Thanks for the reply.
> If you know that a given function uses the calling conventions of a given
> ABI,
> and you know the number of arguments and types, you can directly access the
> stack to get at parameter values. Otherwise, you need to parse debug
> information.
> I suppose you need to extend the debug info reader to be able to forward
> such
> information to tools.
>
I know the arguments and their types. I can get the stackpointer during
runtime but how do I read the stack after that.
Can I read memory just by dereferencing the stack pointer?
Could you point to some functions which will help me in doing so.
Regards,
pankaj
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
