Bug #78165 Add mtr option to run all client applications with valgrind
Submitted: 21 Aug 2015 11:49 Modified: 26 Aug 2015 17:12
Reporter: Tor Didriksen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[21 Aug 2015 11:49] Tor Didriksen
Description:
mtr currently supports valgrind execution of the server, and mysqltest.
We need valgrind execution of other clients as well:
mysqldump, mysqlpump, mysql_upgrade, mysql, mysqlbinlog, etc.

How to repeat:
See all bugs titled 'ASAN: MEMORY LEAK IN .....'
(about 20 different ones)

There are more errors in:
mysql mysql_upgrade mysqlbinlog mysqldump

The new 'mysqlpump' has massive memory leaks.

Suggested fix:
Add a new mtr option:
 valgrind-clients      Run clients started by .test files with valgrind
[26 Aug 2015 17:12] Paul DuBois
Noted in 5.7.9, 5.8.0 changelogs.

mysql-test-run.pl now has an --valgrind-options option that causes
all clients started by .test files to be run with Valgrind.

In addition, several client memory leak issues were fixed.
[27 Aug 2015 10:13] Paul DuBois
Revised changelog entry:

mysql-test-run.pl now has an --valgrind-clients option that causes
all clients started by .test files to be run with valgrind. This
option requires valgrind 3.9 or later.

In addition, several client memory leak issues were fixed.