summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2010-09-27 22:19:15 -0700
committerFather Chrysostomos <sprout@cpan.org>2010-09-27 22:20:27 -0700
commit6904a83fac06ee37f0b2ca19f0658d449bd92ea6 (patch)
tree538db0c9c9ac74363217b30344bf56fe3b19ea20
parent89cf1afaed1c3e82ca93b9fb348b8e5cb995623f (diff)
downloadperl-6904a83fac06ee37f0b2ca19f0658d449bd92ea6.tar.gz
perldelta for [perl #75174] (dirp_dup)
-rw-r--r--pod/perldelta.pod18
1 files changed, 18 insertions, 0 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 66f0ec7d95..1b98619d06 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -118,6 +118,13 @@ has come to rely on the incorrect behavior.
[ List each incompatible change as a =head2 entry ]
+=head2 Directory handles not copied to threads
+
+On systems that do not have a C<fchdir> function, newly-created threads no
+longer inherit directory handles from their parent threads. Such programs
+would probably have crashed anyway
+L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
+
=head1 Deprecations
XXX Any deprecated features, syntax, modules etc. should be listed here.
@@ -605,6 +612,17 @@ It also happened when a glob was assigned to, or returned from, an element
of a tied array or hash
L<[perl #36051]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=36051>.
+=item *
+
+Creating a new thread when directory handles were open used to cause a
+crash, because the handles were not cloned, but simply passed to the new
+thread, resulting in a double free.
+
+Now directory handles are properly, on systems that have a C<fchdir>
+function. On other systems, new threads simply do not inherit directory
+handles from their parent threads
+L<[perl #75154]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75154>.
+
=back
=head1 Known Problems