This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients akuchling, asmodai, mark.dickinson, r.david.murray, skrah
Date 2010-04-16.09:37:59
SpamBayes Score 8.667448e-05
Marked as misclassified No
Message-id <1271410682.61.0.13854711056.issue7384@psf.upfronthosting.co.za>
In-reply-to
Content
Valgrind can be installed by:

cd /usr/ports/devel/valgrind && make install


Then you can do (curses_test.py is your short test program):

1) valgrind --db-attach=yes --suppressions=Misc/valgrind-python.supp ./python curses_test.py

2) valgrind --suppressions=Misc/valgrind-python.supp ./python curses_test.py


Valgrind finds invalid writes. The problem with 1) is that the
terminal is in an unusable state, so controlling gdb isn't possible.

The best thing is probably to use 2) and wade through the unformatted
output starting here:

 ==12043== Invalid write of size 8
 ==12043==    at 0x27A71B7: getwin (in/li /libncursesw.so.8)                                                                             ==12043==    by 0x2A3EAAB: PyCurses_GetWin (_cursesmodule.c:1902)
       ==12043==    by 0x4573FB: PyEval_EvalFrameEx (ceval.c:3833)
                                                                  ==12043==    by 0x457DF9: PyEval_EvalCodeEx (ceval.c:3282)


(I don't have time to do that right now, I might do it later.)
History
Date User Action Args
2010-04-16 09:38:02skrahsetrecipients: + skrah, akuchling, mark.dickinson, asmodai, r.david.murray
2010-04-16 09:38:02skrahsetmessageid: <1271410682.61.0.13854711056.issue7384@psf.upfronthosting.co.za>
2010-04-16 09:38:01skrahlinkissue7384 messages
2010-04-16 09:37:59skrahcreate