ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Write traceback file to the same directory as core file

Browse Source 
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.
This commit is contained in:
Michal Nowak
2020-11-24 17:39:23 +01:00
parent 0f0a006c7e
commit 6428fc26af
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bin/tests/system/run.sh.in
View File

@@ -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 \