MySQL Bugs: #6622: Segfaults, bad memory accesses, etc..

Bug #6622	Segfaults, bad memory accesses, etc..
Submitted:	15 Nov 2004 6:53	Modified:	15 Nov 2004 22:08
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	1.0.13	OS:	Linux (Debian/Linux)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Apparently mysql-admin is accessing a lot of areas of memory that it doesn't actually have access to. Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281321 for examples.

I'm marking this bug with highest priority, because until all errors in mysql admin are fixed then unexpected behaviour and stability problems will continue.

How to repeat:
Run mysql-admin udner `valgrind`. Try the following options,

valgrind -v --leak-check=yes mysql-admin-bin

This will display all of the areas where memory is being accessed incorrectly as well as track down any memory leaks. Make sure you conpile with debug symbols :)

I've fixed most of the problems reported by valgrind, but some of them are from Xlib and other libraries that we don't have control over (try valgrind on any X program, even xlogo). I think they're not important anyway.

Anyway, thanks for reminding about these problems. They're commited now and should be in the next release, which I think won't take long to be released.

Thanks! Valgrind is a great tool to track down these sort of problems... I think that the best way to do actual automatic regression testing is not only make sure that the output is correct, but also that valgrind doesn't find any new errors in the application.