Add variation of compile-pentium-valgrind-max which does not build ndb.
BUILD/compile-pentium-valgrind-max-no-ndb: Disable ndb.
This commit is contained in:
parent
e3320457e1
commit
f972dce2a2
24
BUILD/compile-pentium-valgrind-max-no-ndb
Executable file
24
BUILD/compile-pentium-valgrind-max-no-ndb
Executable file
@ -0,0 +1,24 @@
|
|||||||
|
#! /bin/sh
|
||||||
|
|
||||||
|
path=`dirname $0`
|
||||||
|
. "$path/SETUP.sh"
|
||||||
|
|
||||||
|
extra_flags="$pentium_cflags $debug_cflags $valgrind_flags"
|
||||||
|
extra_configs="$pentium_configs $debug_configs $max_no_ndb_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
|
Loading…
x
Reference in New Issue
Block a user