On Friday 08 July 2011, pankaj pawan wrote:
> 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?
VEX of course can read from memory, see IRExpr_Load.
Or if you ins
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 n
On Thursday 07 July 2011, pankaj pawan wrote:
> Hi Josef,
>
> Thanks for your reply. I did run valgrind with
> guest_chase_thresh = 0 and was able to do capture the calls.
>
> But my doubt was that I can't see the jump statement(is it that
> unconditional jumps are not displayed in IR)
> Sorry
Hi Josef,
Thanks for your reply. I did run valgrind with
guest_chase_thresh = 0 and was able to do capture the calls.
But my doubt was that I can't see the jump statement(is it that
unconditional jumps are not displayed in IR)
Sorry I am new, but an unconditional branch we should just set the I
On Thursday 07 July 2011, pankaj pawan wrote:
> Hi all,
>
> I had doubt regarding the flattened IR for a call instruction. When I try
> and print the IR statements for call instructions, i can see the return
> instruction being written on the stack but i am unable to see how the
> branching is bei
Hi all,
I had doubt regarding the flattened IR for a call instruction. When I try
and print the IR statements for call instructions, i can see the return
instruction being written on the stack but i am unable to see how the
branching is being done.
I can't capture it in Ist_Exit .
Can someone exp
