[pypy-dev] cpyext performance

Maciej Fijalkowski fijall at gmail.com
Thu Jul 5 11:01:51 CEST 2012

On Thu, Jul 5, 2012 at 10:26 AM, Amaury Forgeot d'Arc <amauryfa at gmail.com>wrote:

> 2012/7/5 Stefan Behnel <stefan_ml at behnel.de>
>> Back to that question then:
>> > Is there a way to get readable debugging symbols in a translated PyPy
>> that
>> > would tell me what is being executed?
> I fear that pypy standard distribution calls "strip" on the resulting
> binary.
> You could translate pypy yourself, I'm quite sure it contains debug info
> already and it's quite easy to call "make debug" anyway.
Default build (not the distribution or nightly, you have to trasnlate
yourself), contains debug info. You can do make lldebug to have even more,
but even without it it's usable with valgrind.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120705/52607e1d/attachment-0001.html>

More information about the pypy-dev mailing list