valgrinding with python stuff active / no more false positives with valgrind 3.7?

[Julien Nabet]

On 08/09/2012 11:00, Andrzej J. R. Hunt wrote:
> Hi everyone,
>
> On 09/08/2012 12:49 AM, julien2412 wrote:
>> ...
>> so I get no false positive with Python and/or Java?
>>
>
> Since upgrading my system valgrind no longer gives false positives.
> I'm pretty certain I didn't change any build options when changing
> system: I switched from an older 64 bit release of ubuntu to fedora 17
> (released in May 2012, i.e. pretty modern).
>
> valgrind --version: valgrind-3.7.0
>
> autogen.lastrun:
> --without-help
> --without-myspell-dicts
> --with-max-jobs=4
> --with-num-cpus=4
> --without-junit
> --enable-dbus
>
> gcc --version: gcc (GCC) 4.7.0 20120507 (Red Hat 4.7.0-5)
> python --version: Python 2.7.3 (That's the system python, I think the
> internal one is used though?)
>
> Hope this is helpful. Could it be that valgrind now knows how to deal
> with python?
On pc Debian x86-64 testing updated almost everyday, I've got right now:
valgrind-3.7.0
gcc (Debian 4.7.1-7) 4.7.1
Python 2.7.3rc2

autogen.lastrun:
--with-system-odbc
--enable-ext-mysql-connector
--with-system-mysql
--enable-symbols
--enable-ext-barcode
--enable-ext-diagram
--enable-ext-google-docs
--enable-ext-hunart
--enable-ext-nlpsolver
--enable-ext-ct2n
--enable-ext-numbertext
--enable-ext-oooblogger
--enable-ext-pdfimport
--enable-postgresql-sdbc
--enable-ext-presenter-console
--enable-ext-presenter-minimizer
--enable-ext-report-builder
--enable-ext-scripting-beanshell
--enable-ext-scripting-javascript
--enable-ext-typo
--enable-ext-validator
--enable-ext-watch-window
--enable-ext-wiki-publisher
--enable-dbus
--enable-graphite
--enable-evolution2
--enable-werror
--enable-debug
--enable-dbgutil
--enable-crashdump
--enable-kde4
--enable-dependency-tracking
--enable-online-update

So what to check then?
>
> Cheers,
>
> Andrzej
Julien