c3d4951ef2
Suppress any valgrind error from *anywhere* in the libpython library. There are ***many*** false positives in the python library, making the output of valgrind almost useless without lots of suppressions. Rather than suppress each error piecemeal, we can suppress any error which originates in libpython to cover them all. There will now be corner cases where a bug in gem5 causes some sort of illegal access, etc, within the python library itself, but these sorts of interactions/errors should be very rare. Suppressing the fountain of false positives coming from libpython makes valgrind useable in general, which IMO is a very worthwhile tradeoff. Change-Id: I4869eeeb4aef5884ad52025b52c9616e0541f3e6 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/49530 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com>
61 lines
700 B
Plaintext
61 lines
700 B
Plaintext
{
|
|
python error
|
|
Memcheck:Cond
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Addr1
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Addr2
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Addr4
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Addr8
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Addr16
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Value1
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Value2
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Value4
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Value8
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
python error
|
|
Memcheck:Value16
|
|
obj:*libpython3*
|
|
}
|
|
{
|
|
zlib error
|
|
Memcheck:Cond
|
|
fun:inflateReset2
|
|
}
|