Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
> Did you use the suppression file?
No, I didn't, because I was testing Valgrind on binaries that happened
to be installed on a Linux machine, and had no reason to treat Python
specifically. I see that README.valgrind explains why Python reads
memo
"Esa A E Peuha" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Running Python 2.5.1 under Valgrind is interesting;
What platform and compiler and compiler settings?
--
http://mail.python.org/mailman/listinfo/python-list
|
| does that mean that python's interpretor is a memory beast?
No. The developers have occasionally run Valgrind on Python (or seen the
results of so doing). I believe they have determined that it gives
spurious messages due to some particular features of its coding style or
standards. See
on 11/10/2007 08:38 AM Esa A E Peuha wrote :
> Running Python 2.5.1 under Valgrind is interesting; just starting it and
> then pressing Ctrl-D produces this:
>
> ==27082== ERROR SUMMARY: 713 errors from 56 contexts (suppressed: 10 from 1)
> ==27082== malloc/free: in use at exit: 1,243,153 bytes in
On 10 Nov 2007 02:38:57 +0200, Esa A E Peuha <[EMAIL PROTECTED]> wrote:
>Running Python 2.5.1 under Valgrind is interesting; just starting it and
>then pressing Ctrl-D produces this:
>
>==27082== ERROR SUMMARY: 713 errors from 56 contexts (suppressed: 10 from 1)
>==27082== malloc/free: in use at ex
Running Python 2.5.1 under Valgrind is interesting; just starting it and
then pressing Ctrl-D produces this:
==27082== ERROR SUMMARY: 713 errors from 56 contexts (suppressed: 10 from 1)
==27082== malloc/free: in use at exit: 1,243,153 bytes in 508 blocks.
==27082== malloc/free: 3,002 allocs, 2,494
