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.

diff --git a/bin/tests/system/run.sh.in b/bin/tests/system/run.sh.in
index 481368f9de6a14cd4bc0ca5909bb1983c68f70af..e802332c8cc8f8beae382c2f483e2de097d45657 100644 (file)
--- a/bin/tests/system/run.sh.in
+++ b/bin/tests/system/run.sh.in
@@ -275,7 +275,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_builddir}/libtool" --mode=execute gdb \
                                   -batch \