From f48b221ffaccddbf371a7fcfe8947df2747b514a Mon Sep 17 00:00:00 2001 From: Michal Nowak Date: Tue, 24 Nov 2020 17:39:23 +0100 Subject: [PATCH] Write traceback file to the same directory as core file The traceback files could overwrite each other on systems which do not use different core dump file names for different processes. Prevent that by writing the traceback file to the same directory as the core dump file. These changes still do not prevent the operating system from overwriting a core dump file if the same binary crashes multiple times in the same directory and core dump files are named identically for different processes. (cherry picked from commit 6428fc26af232e0954b65347c1a232e203377321) --- bin/tests/system/run.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/tests/system/run.sh b/bin/tests/system/run.sh index 5101e7f091..2168b9db4d 100644 --- a/bin/tests/system/run.sh +++ b/bin/tests/system/run.sh @@ -283,7 +283,7 @@ if [ -n "$core_dumps" ]; then -- \ "$binary" 2>/dev/null | sed -n '/^Core was generated by/,$p' | cat_d echoinfo "D:$systest:--------------------------------------------------------------------------------" - coredump_backtrace=$(basename "${coredump}")-backtrace.txt + coredump_backtrace="${coredump}-backtrace.txt" echoinfo "D:$systest:full backtrace from $coredump saved in $coredump_backtrace" "${TOP}/libtool" --mode=execute gdb \ -batch \