Bug #69855 | Official way to build with Valgrind (documentation) | ||
---|---|---|---|
Submitted: | 27 Jul 2013 0:51 | Modified: | 17 Jun 2014 11:59 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[27 Jul 2013 0:51]
Roel Van de Paar
[27 Jul 2013 5:13]
MySQL Verification Team
Hello Roel, Thank you for the report. Thanks, Umesh
[27 Jul 2013 5:25]
Roel Van de Paar
Thanks Umesh Please also update http://dev.mysql.com/doc/refman/5.6/en/source-configuration-options.html
[30 Jul 2013 7:05]
Laurynas Biveinis
See http://bugs.mysql.com/bug.php?id=61587
[17 Jun 2014 11:59]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly. http://dev.mysql.com/doc/internals/en/debug-configurations.html To compile in the Valgrind headers and expose the Valgrind API to MySQL code, enable the WITH_VALGRIND option. Combine this with WITH_DEBUG to generate a debug build that is Valgrind-aware: cmake .. -DWITH_DEBUG=1 -DWITH_VALGRIND=1 For MySQL 5.5 and 5.6, also enable Purify flags explicitly (this is unnecessary in 5.7 and up): cmake .. -DWITH_DEBUG=1 -DWITH_VALGRIND=1 \ -DCMAKE_C_FLAGS=-DHave_purify -DCMAKE_CXX_FLAGS=-DHave_purify Also updated http://dev.mysql.com/doc/refman/5.6/en/source-configuration-options.html.