summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Egesdahl <ryan.egesdahl@mongodb.com>2022-03-11 01:04:23 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2022-12-29 03:36:37 +0000
commit1690fbc37427539f1929db30932898e8431b9a34 (patch)
treeea02a055a2c0243156c3a1ce1b9ce4036d71b188
parent12e823ea48b3dd3efee67ffcddd926071df01aa4 (diff)
downloadmongo-1690fbc37427539f1929db30932898e8431b9a34.tar.gz
SERVER-61032 Remove `PATH` variables when executing GDB
(cherry picked from commit 736a3ebe7241a0fbec8734d66b75e74697ce42a5) (cherry picked from commit beb51a7c2e7dc26f31f870e59bd5b9e839392fa1) (cherry picked from commit 4651d9d0b407f15cb5e03934168f9e2efb82c85b)
-rw-r--r--buildscripts/setup_spawnhost_coredump3
1 files changed, 1 insertions, 2 deletions
diff --git a/buildscripts/setup_spawnhost_coredump b/buildscripts/setup_spawnhost_coredump
index 80bdd2bcb66..1f8697fb9f1 100644
--- a/buildscripts/setup_spawnhost_coredump
+++ b/buildscripts/setup_spawnhost_coredump
@@ -3,7 +3,7 @@
cat >> ~/.profile <<EOF
# Coredumps generated by a toolchain built mongodb can be problematic when examined with the system
# gdb.
-export PATH=$PATH:/opt/mongodbtoolchain/v3/bin
+alias gdb='/opt/mongodbtoolchain/v3/bin/gdb'
# As per below, put the user into the appropriate directory. This is where gdb is expected to be
# invoked from.
cd debug
@@ -21,7 +21,6 @@ echo
echo "To examine a core dump, type 'gdb ./<binary> ./<core file>'"
EOF
-export PATH=$PATH:/opt/mongodbtoolchain/v3/bin
echo 'if [ -f ~/.profile ]; then
. ~/.profile
fi' >> .bash_profile