Add perldelta entry about improved kill(9,$pid) on Windows

I'm only adding it because there was a comment at the top of
perldelta that this change was missing an entry.  I'm not
sure it has to be mentioned at all, as it is not a full fix,
just making the issue less likely to occur.

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 37bb32d..051796e 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -7,7 +7,6 @@ b3dbdd48ca2da90bce7f16d545cca54c3dc58f35 (Leon Timmermans)
 44caa20c7d9248fd77483468d77c9b5835e7066e (Craig Berry)
 4581ada393ba58f2b8f438c7b9c336d6c79ec94c (Craig Berry)
 3b28d668e9efe9433c3099521167a6723cbddc26 (Craig Berry)
-82e24582a585cdcc94ac54b3e77a325e7aa89846 (Jan Dubois)
 and any bugs that Karl Williamson has fixed.
 
 =head1 NAME
@@ -608,6 +607,17 @@ already die for arbitrary expressions, but not for simple scalars
 DESTROY methods of objects implementing ties are no longer able to crash by
 accessing the tied variable through a weak reference [perl #86328].
 
+=item *
+
+On Windows, calling kill(9, $child) on a pseudo-process created by the fork()
+emulation is inherently unstable.  It can also be responsible for overriding
+the parent process exit code with a value of '9' if the parent terminates
+right after killing the child.  This condition will now happen a lot less
+often than before.
+
+See also L</"fork() emulation will not wait for signalled children"> for a
+better way to terminate child processes that avoids deadlocks altogether.
+
 =back
 
 =head1 Known Problems