[pypy-dev] Bringing Cython and PyPy closer together
stefan_ml at behnel.de
Sat Feb 18 17:46:09 CET 2012
Stefan Behnel, 18.02.2012 16:29:
> Stefan Behnel, 18.02.2012 09:48:
>> Once we have the test suite runnable, we can set up a PyPy instance on our
>> CI server to get feed-back on any advances.
> I've set up a build job for my development branch here:
> It builds and tests against the latest PyPy-c-jit nightly build, so that we
> get timely feedback for changes on either side.
And now the question is: how do I debug into PyPy? From the nightly build,
I don't get any debugging symbols in gdb, just a useless list of call
addresses (running the ref-counting related "arg_incref" test here):
#0 0x0000000000ef93ef in ?? ()
#1 0x0000000000fca0cb in PyDict_Next ()
#2 0x00007f2564be8f6c in __pyx_pf_10arg_incref_f () from
#3 0x00007f2564be8dd3 in __pyx_pw_10arg_incref_1f () from
#4 0x000000000109e375 in ?? ()
#5 0x00000000010026e4 in ?? ()
[a couple of hundred more skipped that look like the two above]
Aren't debugging symbols enabled for the nightly builds or is this what
PyPy's JIT gives you? I used this file:
And I guess source-level debugging isn't really available for the 37MB pypy
file either, is it?
BTW, I've also run into a problem with distutils under PyPy. The value of
the CFLAGS environment variable is not being split into separate options so
that gcc complains about "-O" not accepting the value "0 -ggdb -fPIC" when
I pass CFLAGS="-O0 -ggdb -fPIC". So I can currently only pass a single
CFLAGS option (my choice obviously being "-ggdb").
More information about the pypy-dev