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
Freeing $_ in grep/map causes a double free #5038
Comments
From sfink@digital-integrity.comCreated by steve@fink.comperl -e 'map{*_=5}1' Perl Info
|
From @schwernOn Wed, Feb 13, 2002 at 01:25:20PM -0800, sfink@digital-integrity.com wrote:
$ perl5.6.1 -e 'map{*_=5}1' (gdb) set args -e 'map{*_=5}1' Program received signal SIGSEGV, Segmentation fault. -- Michael G. Schwern <schwern@pobox.com> http://www.pobox.com/~schwern/ |
From [Unknown Contact. See original ticket]sfink@digital-integrity.com wrote:
Hmm, doing some random typing on my own perl, I see this problem occurs How poorly do these others behave on bleadperl? PS: Here's another bug: Why doesn't strict refs prevent the assignment of the string to the glob? -- |
From @nwc10On Thu, Feb 14, 2002 at 03:52:59AM -0500, Benjamin Goldberg wrote:
Also on bleadperl
All "Attempt to free unreferenced scalar." except the last, which is silent. I think you're right about it occurring with a reference to any scalar: nick@Bagpuss [14766]$ ./perl I don't know where to look for a solution to this bug. Nicholas Clark |
From @jhiOn Thu, Feb 21, 2002 at 06:26:12PM +0000, Nicholas Clark wrote:
Third Degree shows (as of 14815): scope.c: 789: writing invalid heap at byte 0 of 88-byte block This block at address 0x140014210 was allocated at: This block was freed at: -- |
From @chornySame result on 5.12.0. On Wed Feb 13 05:25:44 2002, sfink@digital-integrity.com wrote:
See discussion at http://rt.perl.org/rt3/Ticket/Display.html?id=8527 -- |
From [Unknown Contact. See original ticket]Same result on 5.12.0. On Wed Feb 13 05:25:44 2002, sfink@digital-integrity.com wrote:
See discussion at http://rt.perl.org/rt3/Ticket/Display.html?id=8527 -- |
From @cpansproutOn Wed Feb 13 05:25:44 2002, sfink@digital-integrity.com wrote:
Is this the result of the stack’s not being reference-counted? |
From [Unknown Contact. See original ticket]On Wed Feb 13 05:25:44 2002, sfink@digital-integrity.com wrote:
Is this the result of the stack’s not being reference-counted? |
From @ikegamiOn Sun Oct 10 16:51:32 2010, sprout wrote:
I think so. I've added a dependency to the meta ticket just in case. |
From @cpansprout$ perl5.14.0 -e 'grep { undef *_ } 1' The same applies to map, but it’s the same code. Can we change the definition of SAVE_DEFSV? Flags: Site configuration information for perl 5.14.0: Configured by sprout at Wed May 11 13:45:58 PDT 2011. Summary of my perl5 (revision 5 version 14 subversion 0) configuration: Locally applied patches: @INC for perl 5.14.0: Environment for perl 5.14.0: |
From @cpansproutFixed by 55b5114. |
@cpansprout - Status changed from 'new' to 'resolved' |
From @cpansproutOn Sun Oct 10 17:59:54 2010, ikegami@adaelis.com wrote:
Actually, it’s not. It’s the result of the broken SAVE_DEFSV It turns out that #92254 (which I reported after searching the perl -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
From @cpansproutOn Tue Jan 10 12:26:11 2012, sprout wrote:
Clarification: SAVE_DEFSV was causing *_{SCALAR} not to be -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Tue Jan 10 12:26:11 2012, sprout wrote:
Clarification: SAVE_DEFSV was causing *_{SCALAR} not to be -- Father Chrysostomos |
Migrated from rt.perl.org#8527 (status was 'resolved')
Searchable as RT8527$
The text was updated successfully, but these errors were encountered: