Hi Shubha,
On 29 December 2016 at 22:42, Shubha Ramani via pypy-dev
wrote:
> How do I build with debug symbols (i.e. -g) so that I can inspect core dumps
> when you get a traceback like this ?
Run "make clean; make lldebug" in the directory containing the
generated C sources (.../usession-xyz/te
It's not a bad idea for me. I'm hooking up to a tool made by intel called
"vtune" which requires the function name, function size and function address
from the original python script code. I got the first two from Python
reflection (the way VmProf does it) but I need the third (original script
The id of an object is not necessarily related in any way to the address
of an object in Python.
In RPython, you can convert a function to a low-level function pointer
with llhelper() from rpython.rtyper.annlowlevel. You can call it like
this:
fptr_type = lltype.Ptr(lltype.FuncType([], llty
This is very helpful. Thank you Manuel !
I will try your suggestion.
Shubha
> On Dec 30, 2016, at 8:04 AM, Manuel Jacob wrote:
>
> The id of an object is not necessarily related in any way to the address of
> an object in Python.
>
> In RPython, you can convert a function to a low-level funct
I don't know the signature of the function coming into execute_frame ahead of
time. Therefore as you suggested Manuel,I am leaving the argument is an empty
list []. This doesn't seem to work though. See the assertion error I'm getting
below.All other examples of this technique I see being used a
