Displaying 3 results from an estimated 3 matches for "function_obj".
Did you mean:
function_b
2009 Mar 27
4
[LLVMdev] Connecting JITted code to gdb
...ativeFunction)(PyFrameObject *);
llvm::ExecutionEngine *engine = ...->getExecutionEngine();
NativeFunction native =
(NativeFunction)engine->getPointerToFunction(function);
return native(frame);
However, when I try to step into the call with gdb, I get:
Breakpoint 1, eval_llvm_function (function_obj=0x142f6e0,
frame=0x1350b98) at ../src/Python/ceval.cc:2549
2549 (NativeFunction)engine->getPointerToFunction(function);
(gdb) n
Current language: auto; currently c++
2550 return native(frame);
(gdb) p native
$1 = (NativeFunction) 0x2080010
(gdb) b *0x2080010
Breakpoint 2 at 0x2080010
(gdb) s...
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
...llvm::ExecutionEngine *engine = ...->getExecutionEngine();
> NativeFunction native =
> (NativeFunction)engine->getPointerToFunction(function);
> return native(frame);
>
> However, when I try to step into the call with gdb, I get:
>
> Breakpoint 1, eval_llvm_function (function_obj=0x142f6e0,
> frame=0x1350b98) at ../src/Python/ceval.cc:2549
> 2549 (NativeFunction)engine->getPointerToFunction(function);
> (gdb) n
> Current language: auto; currently c++
> 2550 return native(frame);
> (gdb) p native
> $1 = (NativeFunction) 0x2080010
> (gdb) b *0x2...
2009 Mar 27
2
[LLVMdev] Connecting JITted code to gdb
...ionEngine();
>> NativeFunction native =
>> (NativeFunction)engine->getPointerToFunction(function);
>> return native(frame);
>>
>> However, when I try to step into the call with gdb, I get:
>>
>> Breakpoint 1, eval_llvm_function (function_obj=0x142f6e0,
>> frame=0x1350b98) at ../src/Python/ceval.cc:2549
>> 2549 (NativeFunction)engine->getPointerToFunction(function);
>> (gdb) n
>> Current language: auto; currently c++
>> 2550 return native(frame);
>> (gdb) p native
>>...