summaryrefslogtreecommitdiff
path: root/BUILD
diff options
context:
space:
mode:
authorunknown <guilhem@mysql.com>2003-09-30 00:08:12 +0200
committerunknown <guilhem@mysql.com>2003-09-30 00:08:12 +0200
commit16de8b37f803b48df978af6b06a384e861277c83 (patch)
treef0c25be521149fc66db573d585b6e86eaf5398b8 /BUILD
parent4e24aff59c1c4e8b292d462d90b6a55affb90334 (diff)
downloadmariadb-git-16de8b37f803b48df978af6b06a384e861277c83.tar.gz
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; BUILD/compile-pentium-valgrind-max: a warning note about Valgrind&assembly.
Diffstat (limited to 'BUILD')
-rwxr-xr-xBUILD/compile-pentium-valgrind-max24
1 files changed, 24 insertions, 0 deletions
diff --git a/BUILD/compile-pentium-valgrind-max b/BUILD/compile-pentium-valgrind-max
index 14f57d24841..0201001c959 100755
--- a/BUILD/compile-pentium-valgrind-max
+++ b/BUILD/compile-pentium-valgrind-max
@@ -1,5 +1,17 @@
#! /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"
@@ -11,3 +23,15 @@ extra_configs="$pentium_configs $debug_configs"
extra_configs="$extra_configs --with-berkeley-db --with-innodb --with-embedded-server --with-openssl"
. "$path/FINISH.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.
+********************************************************************************
+"