summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorjwoolley <jwoolley@13f79535-47bb-0310-9956-ffa450edef68>2001-10-01 18:46:40 +0000
committerjwoolley <jwoolley@13f79535-47bb-0310-9956-ffa450edef68>2001-10-01 18:46:40 +0000
commit00faf6a4281257b20ae54bbc99d79b08f8672178 (patch)
tree6ab9d54c8e521f258a44399f0c4ea90983e01703 /CHANGES
parent3f751b36de3061d77fba9160ee74a09e36468291 (diff)
downloadlibapr-00faf6a4281257b20ae54bbc99d79b08f8672178.tar.gz
Fix a potential segfault on Unix when apr_file_close() is called and the
file_cleanup fails. Previously in that situation the cleanup would not be deregistered and therefore it would get run again when the pool went away. Similar behavior in the directory cleanup logic caused segfaults at some point in the past. Reviewed by: Ryan Bloom, Bill Rowe git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@62389 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 213dea7a5..8f044d304 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,5 +1,10 @@
Changes with APR b1
+ *) Fix potential segfault when closing a file on Unix. If
+ apr_file_close() was called and it failed, it would not
+ deregister the file cleanup. Therefore the cleanup would
+ be run again later on a now-invalid descriptor. [Cliff Woolley]
+
*) Introduce apr_pool_lock for debugging, in combination with
ALLOC_USE_MALLOC + DEBUG_WITH_MPROTECT. Only implemented
on Win32 today, very effective for debugging pool constness.