Valgrind 3.3 - Advanced Debugging and Profiling for GNU/Linux applications by J. Seward, N. Nethercote, J. Weidendorfer and the Valgrind Development Team Paperback (6"x9"), 164 pages ISBN 0954612051 RRP £12.95 ($19.95) Get a printed copy>>>

Valgrind 3.3 Buy the book here >>> support free documentation

5.4 Writing suppression files

The basic suppression format is described in 3.5.

The suppression-type (second) line should have the form:

Memcheck:suppression_type

The Memcheck suppression types are as follows:

• Value1, Value2, Value4, Value8, Value16, meaning an uninitialised-value error when using a value of 1, 2, 4, 8 or 16 bytes.
• Cond (or its old name, Value0), meaning use of an uninitialised CPU condition code.
• Addr1, Addr2, Addr4, Addr8, Addr16, meaning an invalid address during a memory access of 1, 2, 4, 8 or 16 bytes respectively.
• Jump, meaning an jump to an unaddressable location error.
• Param, meaning an invalid system call parameter error.
• Free, meaning an invalid or mismatching free.
• Overlap, meaning a ‘src’ / ‘dst’ overlap in memcpy() or a similar function.
• Leak, meaning a memory leak.

‘Param’ errors have an extra information line at this point, which is the name of the offending system call parameter. No other error kinds have this extra line.

The first line of the calling context: for Value and Addr errors, it is either the name of the function in which the error occurred, or, failing that, the full path of the .so file or executable containing the error location. For Free errors, is the name of the function doing the freeing (e.g., free, __builtin_vec_delete, etc). For Overlap errors, is the name of the function with the overlapping arguments (e.g. memcpy(), strcpy(), etc).

Lastly, there's the rest of the calling context.