-
Notifications
You must be signed in to change notification settings - Fork 571
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
'write' on closed filehandle dumps core at end of page #5907
Comments
From @mjdominusCreated by @mjdominusThis program dumps core. #!/usr/bin/perl while (1) { format REPORT_TOP = format REPORT = Perl Info
|
From @TuxOn Tue 10 Sep 2002 05:38, Mark-Jason Dominus (via RT) <perlbug@perl.org> wrote:
l1:/tmp 112 > cat xx.pl use strict; while (1) { format REPORT_TOP = format REPORT = I also waited for over 10 minutes for a core dump without use warnings and HP-UX 11.00, perl-5.8.0 + defined-od patches -- |
From @mjdominus
Great; let's mark it as resolved. I thought maybe I had reported the same bug before, but I wasn't sure. |
From @TuxOn Tue 10 Sep 2002 12:34, Mark-Jason Dominus <mjd@plover.com> wrote:
What perl and what system did you use. I can check others. threading? -- |
From @lizmatAt 12:42 PM 9/10/02 +0200, H.Merijn Brand wrote:
Hmmm... running it here with threaded 5.8.0 under Linux, I see the process I find the process growth suspicious: maybe at one point the growth is Liz |
From @mjdominusCreated by @mjdominusThe write() itself doesn't cause the segv; it's just silently I tried to fix it, but it turned out to be more complicated than I --- t/op/misc.t 2000/12/10 19:48:23 1.1 Perl Info
|
From @hvdsMark-Jason Dominus <mjd@plover.com> wrote: I was going to add this, but of course we don't have t/op/misc.t Hugo |
From @TuxOn Thu 26 Sep 2002 10:51, <hv@crypt.org> wrote:
Format tests are in write.t
-- |
From @jhiJust tested this with bleadperl and no SEGV but yes, a fast process sizze growth |
@jhi - Status changed from 'new' to 'open' |
From @mjdominusApparently fixed in 5.8.0. |
@mjdominus - Status changed from 'open' to 'resolved' |
@mjdominus - Status changed from 'resolved' to 'open' |
From @mjdominusOops, I wasn't paying attention. As Jarkko pointed out, this still |
From @jkeenanOn Mon Sep 09 20:38:29 2002, mjd@plover.com wrote:
When I run this as: perl -d 17099.pl, I get an indefinite series of write() on unopened filehandle REPORT at 17099.pl line 4. (perl 5.16.0) |
From @cpansproutOn Sat May 26 18:24:13 2012, jkeenan wrote:
That’s not suprising, as it has an explicit infinite loop. But if you -- Father Chrysostomos |
From @cpansproutOn Sun Aug 05 13:07:33 2012, sprout wrote:
It’s leaking because a bad file handle causes the output to be held in for(1..5) { warn $^A =~ s'\n'\n'rug; *REPORT = *STDOUT{IO}; format REPORT = Should that change? If not, I think we can mark this as not-a-bug. -- Father Chrysostomos |
Migrated from rt.perl.org#17099 (status was 'open')
Searchable as RT17099$
The text was updated successfully, but these errors were encountered: