source: trunk/essentials/dev-lang/python/Misc/valgrind-python.supp@ 3368

Last change on this file since 3368 was 3225, checked in by bird, 19 years ago

Python 2.5

File size: 5.9 KB
Line 
1#
2# This is a valgrind suppression file that should be used when using valgrind.
3#
4# Here's an example of running valgrind:
5#
6# cd python/dist/src
7# valgrind --tool=memcheck --suppressions=Misc/valgrind-python.supp \
8# ./python -E -tt ./Lib/test/regrtest.py -u bsddb,network
9#
10# You must edit Objects/obmalloc.c and uncomment Py_USING_MEMORY_DEBUGGER
11# to use the preferred suppressions with Py_ADDRESS_IN_RANGE.
12#
13# If you do not want to recompile Python, you can uncomment
14# suppressions for PyObject_Free and PyObject_Realloc.
15#
16# See Misc/README.valgrind for more information.
17
18# all tool names: Addrcheck,Memcheck,cachegrind,helgrind,massif
19{
20 ADDRESS_IN_RANGE/Invalid read of size 4
21 Memcheck:Addr4
22 fun:Py_ADDRESS_IN_RANGE
23}
24
25{
26 ADDRESS_IN_RANGE/Invalid read of size 4
27 Memcheck:Value4
28 fun:Py_ADDRESS_IN_RANGE
29}
30
31{
32 ADDRESS_IN_RANGE/Invalid read of size 8 (x86_64 aka amd64)
33 Memcheck:Value8
34 fun:Py_ADDRESS_IN_RANGE
35}
36
37{
38 ADDRESS_IN_RANGE/Conditional jump or move depends on uninitialised value
39 Memcheck:Cond
40 fun:Py_ADDRESS_IN_RANGE
41}
42
43#
44# Leaks (including possible leaks)
45# Hmmm, I wonder if this masks some real leaks. I think it does.
46# Will need to fix that.
47#
48
49{
50 Handle PyMalloc confusing valgrind (possibly leaked)
51 Memcheck:Leak
52 fun:realloc
53 fun:_PyObject_GC_Resize
54 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
55}
56
57{
58 Handle PyMalloc confusing valgrind (possibly leaked)
59 Memcheck:Leak
60 fun:malloc
61 fun:_PyObject_GC_New
62 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
63}
64
65{
66 Handle PyMalloc confusing valgrind (possibly leaked)
67 Memcheck:Leak
68 fun:malloc
69 fun:_PyObject_GC_NewVar