Displaying 3 results from an estimated 3 matches for "exeuctionengin".
Did you mean:
exeuctionengine
2008 Feb 10
2
[LLVMdev] Instrumenting virtual function calls
...nter
doesn't match any of the functions in my module. I'd hoped to call
ExecutionEngine::getGlobalValueAtAddress to get a Function* for the
virtual function, but ExecutionEngine::getGlobalValueAtAddress returns
null.
If I look up the virtual function that is getting called (with
ExeuctionEngine::getPointerToFunction) it doesn't match the arguments
being passed to my instrumentation. What's a little strange is that
the pointers are somewhat close: getPointerToFunction returns
0x47829a0, but my instrumentation gets 0x477fc10.
What am I missing?
Lines starting with "!&q...
2008 Feb 10
0
[LLVMdev] Instrumenting virtual function calls
...of the functions in my module. I'd hoped to call
> ExecutionEngine::getGlobalValueAtAddress to get a Function* for the
> virtual function, but ExecutionEngine::getGlobalValueAtAddress
> returns null.
>
> If I look up the virtual function that is getting called (with
> ExeuctionEngine::getPointerToFunction) it doesn't match the
> arguments being passed to my instrumentation. What's a little
> strange is that the pointers are somewhat close:
> getPointerToFunction returns 0x47829a0, but my instrumentation gets
> 0x477fc10.
This should basically work....
2008 Feb 13
5
[LLVMdev] Instrumenting virtual function calls
...in my module. I'd hoped to call
>> ExecutionEngine::getGlobalValueAtAddress to get a Function* for the
>> virtual function, but ExecutionEngine::getGlobalValueAtAddress
>> returns null.
>>
>> If I look up the virtual function that is getting called (with
>> ExeuctionEngine::getPointerToFunction) it doesn't match the
>> arguments being passed to my instrumentation. What's a little
>> strange is that the pointers are somewhat close:
>> getPointerToFunction returns 0x47829a0, but my instrumentation gets
>> 0x477fc10.
>
> This shoul...