diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2011-06-21 12:35:14 +0200 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2011-06-21 12:35:14 +0200 |
| commit | 86225089f2d0e82deb368e1688464e8ba84d24cf (patch) | |
| tree | 2ea4ac8481149d9537644246aa0a6d1f359ac03c /tests | |
| parent | de33ec026e505658d613b372ea9d32656ebb86d8 (diff) | |
| download | rsyslog-86225089f2d0e82deb368e1688464e8ba84d24cf.tar.gz rsyslog-86225089f2d0e82deb368e1688464e8ba84d24cf.tar.xz rsyslog-86225089f2d0e82deb368e1688464e8ba84d24cf.zip | |
bugfix: mutex was invalidly left unlocked during action processingv5.8.2
At least one case where this can occur is during thread shutdown, which
may be initiated by lower activity. In most cases, this is quite
unlikely to happen. However, if it does, data structures may be
corrupted which could lead to fatal failure and segfault. I detected
this via a testbench test, not a user report. But I assume that some
users may have had unreproducable aborts that were cause by this bug.
Diffstat (limited to 'tests')
| -rwxr-xr-x | tests/diag.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/diag.sh b/tests/diag.sh index 7651b1de..617118ba 100755 --- a/tests/diag.sh +++ b/tests/diag.sh @@ -10,7 +10,7 @@ #valgrind="valgrind --tool=helgrind --log-fd=1" #valgrind="valgrind --tool=exp-ptrcheck --log-fd=1" #set -o xtrace -#export RSYSLOG_DEBUG="debug nologfuncflow nostdout" +#export RSYSLOG_DEBUG="debug nologfuncflow noprintmutexaction stdout" #export RSYSLOG_DEBUGLOG="log" case $1 in 'init') $srcdir/killrsyslog.sh # kill rsyslogd if it runs for some reason |