-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/2011 08:20 AM, Armin Rigo wrote:
> Ah, sorry. I think I got mistaken in my previous mail. The point is
> that you are debugging *only* a C extension, and not interested in
> debugging any of the rest of PyPy.
Correct. More accurately I hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/2011 05:39 AM, Armin Rigo wrote:
> I think the general problem is that you are trying to approach
> debugging PyPy like you approach debugging a C-written program (say,
> CPython).
Note that I am not trying to debug pypy itself but an extensi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Are you using callgrind or using valgrind for memory checks? The
>> former should work, the latter is rather pointless I think, because
>> RPython manages memory on it's own.
The point is to use valgrind.
>> If you have a bug in cpyext somehow (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2011 01:34 AM, Maciej Fijalkowski wrote:
>>> 32bit pypy works out of the box on valgrind. No idea why 64bit does not
Are you sure it plays nice with the standard memory allocation functions
(malloc/free)? That is unlikely due to use of a GC.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/04/2011 08:54 PM, Roger Binns wrote:
> On 05/02/2011 01:36 PM, Roger Binns wrote:
>> On 05/01/2011 11:30 PM, Antonio Cuni wrote:
>>> you are right, we lack such a document. Do you feel like writing it? :-)
>
>> I&#x
