New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perl 5.10 memory corruption #9345
Comments
From greerga@m-l.orgCreated by greerga@m-l.orgRunning the following program produces memory corruption in Perl - - - 8< - - - 8< - - - Sample of some other interesting values: - - - 8< - - - 8< - - - Affected: Perl Info
|
From @jdhedden
Yuck. I added use strict/warnings, and tried this with 5.11.0 @ 33916: Useless use of array length in void context at bug.pl line 7. |
The RT System itself - Status changed from 'new' to 'open' |
From @rgs2008/5/24 via RT greerga @ m-l. org <perlbug-followup@perl.org>:
Probably a bug in the in-place sort optimisation code. It's quite hard I see that C<@x = (0) x 1024> doesn't cause the bug, because the array It would maybe be helpful to have a binary search for the patch... |
From @moritzRafael Garcia-Suarez wrote:
d29831c62746f36a2610ac8c3aa68b21181486bb is first bad commit p4raw-id: //depot/perl@24784 :100644 100644 e5cbe2f4834901b0715cd6ad5aeb31a6e156a736 This is my first bisect, so I'm not 100% sure I did it right. HTH anyway, |
From @rgs2008/5/26 Moritz Lenz <moritz@casella.verplant.org>:
Well, that doesn't mut the custard for me. In other words, if I revert |
From @iabynOn Mon, May 26, 2008 at 12:27:22PM +0200, Rafael Garcia-Suarez wrote:
Hopefully fixed now: Change 33937 by davem@davem-pigeon on 2008/05/27 00:12:52 [perl #54758] Perl 5.10 memory corruption Affected files ... ... //depot/perl/pp_sort.c#79 edit Differences ... ==== //depot/perl/pp_sort.c#79 (text) ==== @@ -1557,11 +1557,12 @@ -- |
From @greergaI can confirm that Dave's patch fixes the original script that was -George |
@doughera88 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#54758 (status was 'resolved')
Searchable as RT54758$
The text was updated successfully, but these errors were encountered: