GNOME Bugzilla – Bug 489269
valgrind option parameter invalid for valgrind 2.2
Last modified: 2008-04-13 20:46:43 UTC
on linux, "--leak-check=full" and "--gen-suppressions=all" are invalid on latest valgrind version. Change valgrind option parameter. Changed files: common/check.mak Motorola would like to contribute Gstreamer patch to the Gstreamer open source community project. Please find attached the patch applicable for Gstreamer. For any questions, please feel free to contact (Zhao Liang "e3423c@motorola.com", Shi Ling "w20230@motorola.com").
Created attachment 97690 [details] [review] check.mak.patch
> on linux, "--leak-check=full" and "--gen-suppressions=all" are invalid on > latest valgrind version. What valgrind version is that exactly? I can't find any evidence of such a change in valgrind SVN (rev. 7036), ie. valgrind 3.3.0-SVN
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Please provide us with the version of valgrind you are using so that we can detect it and adapt accordingly. [This bug is part of Fluendo support for Motorola.]
our valgrind is 2.2.0, no valgrind version check in gstreamer configure
I can confirm that in version 2.2.0 leak-check had only the yes/no value pair. In latest version they've added full. It seems that full and yes are equivalent. For gen-suppressions this is the same thing, all have been added. But in that case yes and all do not seem to have the same behavior. Maybe we could require valgrind >= 3.0 to enable the valgrind features or we could detect valgrind versions and adapt the parameters. Suggestions. ?
I think detecting valgrind versions is better for us, because our linux version is restricted, we can make a change, submit patch.
Thanks for the clarification. I've updated the requirements now: 2008-04-13 Tim-Philipp Müller <tim at centricular dot net> * m4/gst-args.m4: * m4/gst-valgrind.m4: Bump valgrind requirement to 3.0 (which was released in August 2005). Fixes #489269. Also, check for version >=REQ and not >REQ.