[pypy-dev] "import signal" fails when running PyPy interpreted

Amaury Forgeot d'Arc amauryfa at gmail.com
Mon Mar 12 10:47:54 CET 2012

2012/3/12 Stefan Behnel <stefan_ml at behnel.de>:
> Rethinking this some more - I'd be *really* happy if everything was just C.
> Armin noted that the RPython-to-C translation is basically a 1:1 mapping
> (plus type specialisation). So, if the generated C code is any usable and
> if the nightly builds had debugging symbols in them, I could just run gdb
> and callgrind over them and they would pinpoint the obvious problems
> immediately.
> Would that work? And if so, could someone enable that?

Yes, it works, but the result is not so easy to debug and understand.

This said, compliing pypy is not so difficult on a Linux machine; and you only
need to translate with the -O2 option, the JIT is not useful to debug cpyext.

Amaury Forgeot d'Arc

More information about the pypy-dev mailing list