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
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
