[prev in list] [next in list] [prev in thread] [next in thread]
List: pypy-dev
Subject: Re: [pypy-dev] Py_DecRef() in cpyext
From: Armin Rigo <arigo () tunes ! org>
Date: 2012-02-26 12:29:50
Message-ID: CAMSv6X1WXXHE02JjzW7ZN9+yE_wijfw1xD8DO_T5GObcok14aA () mail ! gmail ! com
[Download RAW message or body]
Hi,
On Sun, Feb 26, 2012 at 12:31, Stefan Behnel <stefan_ml@behnel.de> wrote:
> Interesting. Given PyPy's reputation of taking tons of resources to build,
> I assume you apply WPA to the sources in order to map them to C?
Yes. Please read more about it starting for example from here:
http://doc.pypy.org/en/latest/architecture.html
> Then why
> wouldn't I get better traces from gdb and valgrind for the generated code?
> Is it just that the nightly builds lack debugging symbols?
Yes. With a proper debugging build you get at least the intermediate
C code. Not extremely readable but at least you can follow it.
A bient=F4t,
Armin.
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic