diff options
| author | unknown <monty@narttu.mysql.fi> | 2003-10-08 21:50:05 +0300 |
|---|---|---|
| committer | unknown <monty@narttu.mysql.fi> | 2003-10-08 21:50:05 +0300 |
| commit | d1d07c99d7dc1f443776a48e66aa471b3b4535e4 (patch) | |
| tree | caac541df5c696ac2dd3b9e21880442e8961b4dc /BUILD/compile-pentium-valgrind-max | |
| parent | 44e3cbcfeb14dd45b2eea154a8a602a5851cfac9 (diff) | |
| download | mariadb-git-d1d07c99d7dc1f443776a48e66aa471b3b4535e4.tar.gz | |
Indentation cleanups
Remove wait_if_global_read_lock on commit as this can cause deadlocks
BUILD/FINISH.sh:
Cleanup
BUILD/SETUP.sh:
Cleanup
BUILD/compile-pentium-valgrind-max:
Don't write message twice
mysql-test/r/innodb.result:
Removed failure as this can cause deadlocks
mysql-test/r/rpl_max_relay_size.result:
Make test repeatable
mysql-test/t/innodb.test:
Removed failure as this can cause deadlocks
mysql-test/t/rpl_max_relay_size.test:
Removed failure as this can cause deadlocks
sql/handler.cc:
Remove wait_if_global_read_lock as this can cause deadlocks
sql/opt_range.cc:
Indentation cleanup
sql/sql_db.cc:
Comment cleanup
sql/sql_parse.cc:
Comment cleanup
sql/sql_repl.cc:
Indentation cleanup
sql/sql_select.cc:
Indentation cleanup
Diffstat (limited to 'BUILD/compile-pentium-valgrind-max')
| -rwxr-xr-x | BUILD/compile-pentium-valgrind-max | 32 |
1 files changed, 11 insertions, 21 deletions
diff --git a/BUILD/compile-pentium-valgrind-max b/BUILD/compile-pentium-valgrind-max index f752af86d1c..f47061b95dd 100755 --- a/BUILD/compile-pentium-valgrind-max +++ b/BUILD/compile-pentium-valgrind-max @@ -1,17 +1,5 @@ #! /bin/sh -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. -******************************************************************************** -" - path=`dirname $0` . "$path/SETUP.sh" @@ -24,14 +12,16 @@ extra_configs="$extra_configs --with-berkeley-db --with-innodb --without-isam -- . "$path/FINISH.sh" -echo "\ -******************************************************************************** +if test -z "$just_print" +then + 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. -******************************************************************************** -" +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 |