mirrors/mongodb
mirrors/mongodb
0
0
Fork 0
mirror of https://github.com/mongodb/mongo.git synced 2024-11-25 09:19:32 +01:00
Code Issues Releases Activity

SERVER-61032 Ensure all current references to GDB are for v3 toolchain

Browse Source
This commit is contained in:
Ryan Egesdahl 2022-03-03 15:00:52 +00:00 committed by Evergreen Agent
parent c9a74181ad
commit 65cf760916
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
buildscripts/resmokelib/hang_analyzer/dumper.py
View File

@ -332,7 +332,7 @@ class GDBDumper(Dumper):
def _find_debugger(self, debugger):
"""Find the installed debugger."""
return find_program(debugger, ['/opt/mongodbtoolchain/gdb/bin', '/usr/bin'])
return find_program(debugger, ['/opt/mongodbtoolchain/v3/bin', '/usr/bin'])
def _prefix(self):
"""Return the commands to set up a debugger process."""

2
buildscripts/resmokelib/powercycle/remote_hang_analyzer/__init__.py
View File

@ -48,7 +48,7 @@ class RunHangAnalyzerOnRemoteInstance(PowercycleCommand):
# we don't want to evaluate the local python variable, but instead pass the python string
# so the remote host will use the right python when the virtualenv is sourced.
cmds = f"{cmds}; cd {remote_dir}"
cmds = f"{cmds}; PATH=\"/opt/mongodbtoolchain/gdb/bin:$PATH\" python buildscripts/resmoke.py hang-analyzer {hang_analyzer_option}"
cmds = f"{cmds}; PATH=\"/opt/mongodbtoolchain/v3/bin:$PATH\" python buildscripts/resmoke.py hang-analyzer {hang_analyzer_option}"
self.remote_op.operation(SSHOperation.SHELL, cmds, None)
file_param = []

4
buildscripts/setup_spawnhost_coredump
View File

@ -14,7 +14,7 @@ cat >> ~/.profile <<EOF
cat ~/.setup_spawnhost_coredump_progress
# Coredumps generated by a toolchain built mongodb can be problematic when examined with the system
# gdb.
export PATH=/opt/mongodbtoolchain/gdb/bin:$PATH
export PATH=/opt/mongodbtoolchain/v3/bin:$PATH
# As per below, put the user into the appropriate directory. This is where gdb is expected to be
# invoked from.
cd debug
@ -33,7 +33,7 @@ echo "To examine a core dump, type 'gdb ./<binary> ./<core file>'"
cat ~/.setup_spawnhost_coredump_progress
EOF
export PATH=/opt/mongodbtoolchain/gdb/bin:$PATH
export PATH=/opt/mongodbtoolchain/v3/bin:$PATH
echo 'if [ -f ~/.profile ]; then
. ~/.profile
fi' >> .bash_profile

2
evergreen/failed_unittests_gather.sh
View File

@ -19,7 +19,7 @@ for core_file in $core_files; do
# A core file name does not always have the executable name that generated it.
# See http://stackoverflow.com/questions/34801353/core-dump-filename-gets-thread-name-instead-of-executable-name-with-core-pattern
# On platforms with GDB, we get the binary name from core file
gdb=/opt/mongodbtoolchain/gdb/bin/gdb
gdb=/opt/mongodbtoolchain/v3/bin/gdb
if [ -f $gdb ]; then
binary_file=$($gdb -batch --quiet -ex "core $core_file" 2> /dev/null | grep "Core was generated" | cut -f2 -d "\`" | cut -f1 -d "'" | cut -f1 -d " ")
binary_file_locations=$binary_file

4
evergreen/hang_analyzer.sh
View File

@ -14,8 +14,8 @@ else
fi
activate_venv
echo "Calling the hang analyzer: PATH=\"/opt/mongodbtoolchain/gdb/bin:$PATH\" $python buildscripts/resmoke.py hang-analyzer $hang_analyzer_option"
PATH="/opt/mongodbtoolchain/gdb/bin:$PATH" $python buildscripts/resmoke.py hang-analyzer $hang_analyzer_option
echo "Calling the hang analyzer: PATH=\"/opt/mongodbtoolchain/v3/bin:$PATH\" $python buildscripts/resmoke.py hang-analyzer $hang_analyzer_option"
PATH="/opt/mongodbtoolchain/v3/bin:$PATH" $python buildscripts/resmoke.py hang-analyzer $hang_analyzer_option
# Call hang analyzer for tasks that are running remote mongo processes
if [ -n "${private_ip_address}" ]; then