6a481e9253
Executables and .debug files are now extracted into the bin directory. The contents of the bin directory are symlinked into the parent debug directory.
106 lines
4.6 KiB
Bash
Executable File
106 lines
4.6 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
cd $HOME # workaround EVG-12829
|
|
|
|
# Communicate to users that logged in before the script started that nothing is ready.
|
|
wall "The setup_spawnhost_coredump script has just started setting up the debugging environment."
|
|
|
|
# Write this file that gets cat'ed on login to communicate to users logging in if this setup script is still running.
|
|
echo '+-----------------------------------------------------------------+' > ~/.setup_spawnhost_coredump_progress
|
|
echo '| The setup script is still setting up data files for inspection. |' >> ~/.setup_spawnhost_coredump_progress
|
|
echo '+-----------------------------------------------------------------+' >> ~/.setup_spawnhost_coredump_progress
|
|
|
|
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
|
|
# As per below, put the user into the appropriate directory. This is where gdb is expected to be
|
|
# invoked from.
|
|
cd debug
|
|
echo "Debuggable binaries:"
|
|
ls -l mongo* | grep -v debug$
|
|
for item in "mongo" "mongod" "mongos"; do
|
|
echo "\${item} core dumps:"
|
|
ls -l dump_\${item}.*
|
|
done
|
|
|
|
echo "Core dumps from unknown processes (crashed processes typically found here):"
|
|
ls -l dump_* | grep -v mongo
|
|
|
|
echo
|
|
echo "To examine a core dump, type 'gdb ./<binary> ./<core file>'"
|
|
cat ~/.setup_spawnhost_coredump_progress
|
|
EOF
|
|
|
|
export PATH=/opt/mongodbtoolchain/gdb/bin:$PATH
|
|
echo 'if [ -f ~/.profile ]; then
|
|
. ~/.profile
|
|
fi' >> .bash_profile
|
|
|
|
# Make a directory on the larger EBS volume. Soft-link it under the home directory. The smaller home
|
|
# volume can have trouble particularly with coredumps from sharded timeouts.
|
|
mkdir /data/debug
|
|
ln -s /data/debug .
|
|
cd debug
|
|
|
|
# As the name suggests, pretty printers. Primarily for boost::optional<T>
|
|
git clone git@github.com:ruediger/Boost-Pretty-Printer.git &
|
|
|
|
# Discover and unarchive necessary files and source code. This will put mongo binaries and their
|
|
# partner .debug files in the same `debug/bin` directory. The `bin` directory will later be symbolic
|
|
# linked into the top-level (`debug`) directory. Shared library files and their debug symbols will
|
|
# be dumped into a `debug/lib` directory for tidiness. The mongo `<reporoot>/src/` directory is soft
|
|
# linked as `debug/src`. The .gdbinit file assumes gdb is being run from the `debug` directory.
|
|
BIN_ARCHIVE=`ls /data/mci/artifacts-*archive_dist_test*/mongo-*.tgz`
|
|
tar --wildcards --strip-components=1 -xzf $BIN_ARCHIVE '*/bin/mongod' '*/bin/mongos' '*/bin/mongo' '*/bin/mongobridge' &
|
|
tar --wildcards --strip-components=1 -xzf $BIN_ARCHIVE '*/lib/*' &
|
|
DBG_ARCHIVE=`ls /data/mci/artifacts-*archive_dist_test_debug/debugsymbols-*.tgz`
|
|
tar --wildcards --strip-components=1 -xzf $DBG_ARCHIVE '*/bin/mongod.debug' '*/bin/mongos.debug' '*/bin/mongo.debug' '*/bin/mongobridge.debug' &
|
|
tar --wildcards --strip-components=1 -xzf $DBG_ARCHIVE '*/lib/*' &
|
|
UNITTEST_ARCHIVE=`ls /data/mci/artifacts-*run_unittests/mongo-unittests-*.tgz`
|
|
tar --wildcards --strip-components=0 -xzf $UNITTEST_ARCHIVE 'bin/*' &
|
|
tar --wildcards -xzf $UNITTEST_ARCHIVE 'lib/*' &
|
|
|
|
SRC_DIR=`find /data/mci/ -maxdepth 1 | grep source`
|
|
ln -s $SRC_DIR/.gdbinit .
|
|
ln -s $SRC_DIR/src src
|
|
ln -s $SRC_DIR/buildscripts buildscripts
|
|
|
|
# Install pymongo to get the bson library for pretty-printers.
|
|
/opt/mongodbtoolchain/v3/bin/pip3 install -r $SRC_DIR/etc/pip/dev-requirements.txt &
|
|
|
|
COREDUMP_ARCHIVE=`ls /data/mci/artifacts-*/mongo-coredumps-*.tgz`
|
|
tar -xzf $COREDUMP_ARCHIVE &
|
|
echo "Waiting for background processes to complete."
|
|
wait
|
|
|
|
# Symbolic linking all of the executable files is sufficient for `gdb ./mongod ./dump_mongod.core`
|
|
# to succeed. This inadvertantly also links in the ".debug" files which is unnecessary, but
|
|
# harmless. gdb expects the .debug files to live adjacent to the physical binary.
|
|
ln -s bin/* ./
|
|
|
|
cat >> ~/.gdbinit <<EOF
|
|
set auto-load safe-path /
|
|
set solib-search-path ./lib/
|
|
set pagination off
|
|
set print object on
|
|
set print static-members off
|
|
set print pretty on
|
|
|
|
python
|
|
import sys
|
|
sys.path.insert(0, './Boost-Pretty-Printer')
|
|
import boost
|
|
boost.register_printers(boost_version=(1,70,0))
|
|
end
|
|
EOF
|
|
|
|
echo "dir $HOME/debug" >> ~/.gdbinit
|
|
|
|
# Empty out the progress script that warns users about the set script still running when users log in.
|
|
echo "" > ~/.setup_spawnhost_coredump_progress
|
|
# Alert currently logged in users that this setup script has completed. Logging back in will ensure any
|
|
# paths/environment variables will be set as intended.
|
|
wall "The setup_spawnhost_coredump script has completed, please relogin to ensure the right environment variables are set."
|