On Win32,
Perl can now use non-IFS compatible LSPs,
which allows Perl to work in conjunction with firewalls such as McAfee Guardian.
For full details see the file README.win32,
particularly if you're running Win95.

The regexp engine is now more robust when given invalid utf8 input,
as is sometimes generated by buggy XS modules.

foreach on threads::shared array used to be able to crash Perl.
This bug has now been fixed.

A regexp in STDOUT's destructor used to coredump,
because the regexp pad was already freed.
This has been fixed.

goto & is now more robust - bugs in deep recursion and chained goto & have been fixed.

Using delete on an array no longer leaks memory.
A pop of an item from a shared array reference no longer causes a leak.

eval_sv() failing a taint test could corrupt the stack - this has been fixed.

On platforms with 64 bit pointers numeric comparison operators used to erroneously compare the addresses of references that are overloaded,
rather than using the overloaded values.
This has been fixed.

read into a UTF8-encoded buffer with an offset off the end of the buffer no longer mis-calculates buffer lengths.

Although Perl has promised since version 5.8 that sort() would be stable,
the two cases sort {$b cmp $a} and sort {$b <=> $a} could produce non-stable sorts.
This is corrected in perl5.8.6.

If you find what you think is a bug,
you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at http://bugs.perl.org.
There may also be information at http://www.perl.org,
the Perl Home Page.

If you believe you have an unreported bug,
please run the perlbug program included with your release.
Be sure to trim your bug down to a tiny but sufficient test case.
Your bug report,
along with the output of perl -V,
will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
You can browse and search the Perl 5 bugs at http://bugs.perl.org/