mariadb/BUILD/compile-pentium-valgrind-max

#! /bin/sh

path=`dirname $0`
. "$path/SETUP.sh"

extra_flags="$pentium_cflags $debug_cflags $max_cflags -USAFEMALLOC -UFORCE_INIT_OF_VARS -DHAVE_purify -DMYSQL_SERVER_SUFFIX=-valgrind-max"
c_warnings="$c_warnings $debug_extra_warnings"
cxx_warnings="$cxx_warnings $debug_extra_warnings"
extra_configs="$pentium_configs $debug_configs"

# We want to test isam when building with valgrind
extra_configs="$extra_configs $max_leave_isam_configs --with-isam"

. "$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
Added back old LARGEFILE handling Fixed reference to freed memory in acl_init()/grant_init() Fixed possible memory leak. (Could only happen in very strange circumstances) Fixed bug in ALTER TABLE with BDB tables Updated mysql-test for valgrind 2002-10-29 21:59:03 +02:00			`#! /bin/sh`

			path=`dirname $0`
			`. "$path/SETUP.sh"`

Fix all BUILD/max scripts to use -DBIG_TABLES, like our real Max builds do. (Simpler fix than last commit -- no need to mess with base_cxxflags.) 2005-01-19 10:24:51 -08:00			`extra_flags="$pentium_cflags $debug_cflags $max_cflags -USAFEMALLOC -UFORCE_INIT_OF_VARS -DHAVE_purify -DMYSQL_SERVER_SUFFIX=-valgrind-max"`
Added back old LARGEFILE handling Fixed reference to freed memory in acl_init()/grant_init() Fixed possible memory leak. (Could only happen in very strange circumstances) Fixed bug in ALTER TABLE with BDB tables Updated mysql-test for valgrind 2002-10-29 21:59:03 +02:00			`c_warnings="$c_warnings $debug_extra_warnings"`
			`cxx_warnings="$cxx_warnings $debug_extra_warnings"`
			`extra_configs="$pentium_configs $debug_configs"`

CLIENT_MULTI_QUERIES -> CLIENT_MULTI_STATEMENTS New multi-key-cache handling. This was needed becasue the old one didn't work reliable with MERGE tables. ALTER TABLE table_name ... CHARACTER SET ... now changes all char/varchar/text columns to the given character set (One must use ALTER TABLE ... DEFAULT CHARACTER SET ... to change the default character set) Fixed that have_compress is detected properly (fixes problems with func_compress.test on platforms without zlib) New syntax for CACHE INDEX ('keys' is optional if no index name is given and one mentions the key cache name only ones) Removed compiler warnings Added mysql_set_server_option() to allow clients like PHP to easaily set/reset the multi-statement flag. 2003-11-18 13:47:27 +02:00			`# We want to test isam when building with valgrind`
Put flags for -max building in BUILD/SETUP.sh so they are consistent across all architectures, and in sync with the flags used to build the MySQL Max packages. Also back-port AMD64 build scripts from 5.0. 2005-01-13 09:05:23 -08:00			`extra_configs="$extra_configs $max_leave_isam_configs --with-isam"`
Added back old LARGEFILE handling Fixed reference to freed memory in acl_init()/grant_init() Fixed possible memory leak. (Could only happen in very strange circumstances) Fixed bug in ALTER TABLE with BDB tables Updated mysql-test for valgrind 2002-10-29 21:59:03 +02:00
			`. "$path/FINISH.sh"`
A note that Valgrind does not give a good stacktrace when the problem is involving an assembly function. Testcase was BUG#1194 SELECT @a:=1; SELECT @a, @a:=1; 2003-09-30 00:08:12 +02:00
Indentation cleanups Remove wait_if_global_read_lock on commit as this can cause deadlocks 2003-10-08 21:50:05 +03:00			`if test -z "$just_print"`
			`then`
Fixed access to uninitialized memory in protocol::store_time 2003-11-04 14:59:38 +02:00			`set +v +x`
Indentation cleanups Remove wait_if_global_read_lock on commit as this can cause deadlocks 2003-10-08 21:50:05 +03:00			`echo "\`
			`******************************************************************************`
A note that Valgrind does not give a good stacktrace when the problem is involving an assembly function. Testcase was BUG#1194 SELECT @a:=1; SELECT @a, @a:=1; 2003-09-30 00:08:12 +02:00			`Note that by default BUILD/compile-pentium-valgrind-max calls 'configure' with`
			`--enable-assembler. When Valgrind detects an error involving an assembly`
Indentation cleanups Remove wait_if_global_read_lock on commit as this can cause deadlocks 2003-10-08 21:50:05 +03:00			`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`