On May 7, 2008, at 10:46 PM, Stefan Behnel wrote:
> Hi,
>
> Jim Kleckner wrote:
>> Jim Kleckner wrote:
>>> Stefan Behnel wrote:
>>> ...
>>>> For debugging, I mostly use print and unit tests for Python and
>>>> print, tests
>>>> and valgrind for Cython, so I can't really comment on the debugging
>>>> environments (which actually *are* available for emacs).
>>> Stefan, do you have some tips for Valgrind?
>>> Do you have a suppression file that you like?
>>>
>>> I ran valgrind again and found a sea of messages with a small number
>>> of suspicious ones.
>>> Two of them have the form:
>>> __pyx_4 = PyObject_Call(__pyx_12, __pyx_empty_tuple, NULL); if
>>> (unlikely(!__pyx_4)) {
>>> which suggests that the NULL is fooling Valgrind in some way.
>>>
>>> This page might be a good place to put such things as suppression
>>> files:
>>> http://wiki.cython.org/UsingValgrindToDebug
>>>
>>
>> This page explains some of the PyMalloc issues:
>> http://svn.python.org/projects/python/trunk/Misc/README.valgrind
>
> Yes, that's where we took the suppression file from that we use for
> lxml.
>
> http://codespeak.net/svn/lxml/trunk/valgrind-python.supp
I bet turning off string interning, etc. would help clean up lots of
the noise too.
- Robert
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
