mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 03:52:35 +01:00
963b19861f
TO DO: Enable this in CMake-based builds. ------------------------------------------------------------ revno: 3474 revision-id: marko.makela@oracle.com-20100520104042-ma2nsscqdvwoph8k parent: marko.makela@oracle.com-20100519081618-h38q02qxuvcowbtk committer: Marko Mäkelä <marko.makela@oracle.com> branch nick: 5.1-innodb timestamp: Thu 2010-05-20 13:40:42 +0300 message: Bug#53593: Add some instrumentation to improve Valgrind sensitivity BUILD/*: Add valgrind_configs=--with-valgrind. BUILD/*: Remove -USAFEMALLOC from valgrind_flags. configure.in: Add AC_ARG_WITH(valgrind) and HAVE_VALGRIND. include/my_sys.h: Define a number of MEM_ wrappers for VALGRIND_ functions. include/my_sys.h: Make TRASH do MEM_UNDEFINED(). include/m_string.h: Remove unused macro bzero_if_purify(A,B). _mymalloc(): Declare MEM_UNDEFINED() on the allocated memory. _myfree(): Declare MEM_NOACCESS() on the freed memory. storage/innobase/include/univ.i: Enable UNIV_DEBUG_VALGRIND based on HAVE_VALGRIND rather than HAVE_purify. Possible things to do: * In my_global.h, remove the defined(HAVE_purify) condition from the _WIN32 uint3korr(). * In my_global.h *int*korr(), use | instead of + in order to keep the Valgrind V bits accurate * Consider replacing HAVE_purify with HAVE_VALGRIND * Use VALGRIND_CREATE_BLOCK, VALGRIND_DISCARD in mem_root and similar places
24 lines
888 B
Bash
Executable file
24 lines
888 B
Bash
Executable file
#! /bin/sh
|
|
|
|
path=`dirname $0`
|
|
. "$path/SETUP.sh"
|
|
|
|
extra_flags="$amd64_cflags $debug_cflags $valgrind_flags"
|
|
extra_configs="$amd64_configs $debug_configs $valgrind_configs $max_configs"
|
|
|
|
. "$path/FINISH.sh"
|
|
|
|
if test -z "$just_print"
|
|
then
|
|
set +v +x
|
|
echo "\
|
|
******************************************************************************
|
|
Note that by default BUILD/compile-pentium-valgrind-max calls 'configure' with
|
|
--enable-assembler. When Valgrind detects an error involving an assembly
|
|
function (for example an uninitialized value used as an argument of an
|
|
assembly function), Valgrind will not print the stacktrace and 'valgrind
|
|
--gdb-attach=yes' will not work either. If you need a stacktrace in those
|
|
cases, you have to run BUILD/compile-pentium-valgrind-max with the
|
|
--disable-assembler argument.
|
|
******************************************************************************"
|
|
fi
|