Changeset 745 for trunk/server/source4/.valgrind_suppressions
- Timestamp:
 - Nov 27, 2012, 4:43:17 PM (13 years ago)
 - Location:
 - trunk/server
 - Files:
 - 
      
- 2 edited
 
- 
          
  . (modified) (1 prop)
 - 
          
  source4/.valgrind_suppressions (modified) (1 diff)
 
 
Legend:
- Unmodified
 - Added
 - Removed
 
- 
      
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 581,587,591,594,597,600,615,618,740  
 - Property svn:mergeinfo changed
 - 
      
trunk/server/source4/.valgrind_suppressions
r414 r745 84 84 fun:__libc_dlsym 85 85 } 86 87 # 88 # Tests from valgrind-python.supp (distributed with python): 89 # 90 # These try and suppress these errors 91 # 92 93 # all tool names: Addrcheck,Memcheck,cachegrind,helgrind,massif 94 { 95 ADDRESS_IN_RANGE/Invalid read of size 4 96 Memcheck:Addr4 97 fun:Py_ADDRESS_IN_RANGE 98 } 99 100 { 101 ADDRESS_IN_RANGE/Invalid read of size 4 102 Memcheck:Value4 103 fun:Py_ADDRESS_IN_RANGE 104 } 105 106 { 107 ADDRESS_IN_RANGE/Invalid read of size 8 (x86_64 aka amd64) 108 Memcheck:Value8 109 fun:Py_ADDRESS_IN_RANGE 110 } 111 112 { 113 ADDRESS_IN_RANGE/Conditional jump or move depends on uninitialised value 114 Memcheck:Cond 115 fun:Py_ADDRESS_IN_RANGE 116 } 117 118 # 119 # Leaks (including possible leaks) 120 # Hmmm, I wonder if this masks some real leaks. I think it does. 121 # Will need to fix that. 122 # 123 124 { 125 Handle PyMalloc confusing valgrind (possibly leaked) 126 Memcheck:Leak 127 fun:realloc 128 fun:_PyObject_GC_Resize 129 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING 130 } 131 132 { 133 Handle PyMalloc confusing valgrind (possibly leaked) 134 Memcheck:Leak 135 fun:malloc 136 fun:_PyObject_GC_New 137 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING 138 } 139 140 { 141 Handle PyMalloc confusing valgrind (possibly leaked) 142 Memcheck:Leak 143 fun:malloc 144 fun:_PyObject_GC_NewVar 145 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING 146 } 147  
  Note:
 See   TracChangeset
 for help on using the changeset viewer.
  