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
Random error msgs in shutdown? #6298
Comments
From bsb@strategicdata.com.auCreated by bsb@strategicdata.com.auThis is a bug report for perl from bsb@strategicdata.com.au, ----------------------------------------------------------------- Hi, Sample symptoms, this printed on stderr: I've pared down my the original problem but it still uses DBI(1.21) Some of the code versions from my error hunting are in During the hunt I got "*Regexp::DESTROY.", "Out of memory!", Adding a print at various points, or even changing the printed strings Adding an exit would cover the error messages. Errors always seemed the same on repeated runs of the same code. At one stage I got a different result depending whether I ran [14:20 sb]$ head -n 1 a Here's the code I stopped with, output after the __END__: #!/usr/bin/perl -w sub create { $dbh->do('drop table if exists slot'); { __END__ [14:48 sb]$ perl a Thanks, Brad Perl Info
|
From @eserteBrad Bowman (via RT) <perlbug-followup@perl.org> writes:
With 5.6.1 I get the following output: $ perl5.6.1 x.pl With 5.8.0 there is no problem: $ perl5.8.0 x.pl Regards,
-- tktimex - project time manager |
From bsb@strategicdata.com.auHere's a still simpler test script. Using HandleError + confess was crashing and looping #!/usr/bin/perl -wl eval { __END__ $ ./carp_bug.pl Use of uninitialized value in subroutine entry. |
From @HugmeirOn Tue Feb 25 02:45:49 2003, bsb@strategicdata.com.au wrote:
I can't reproduce this on 5.14.2, DBI 1.617, DBD::CSV 0.33; And since |
@cpansprout - Status changed from 'open' to 'resolved' |
From @TuxOn Sun, 29 Apr 2012 03:41:00 -0700, "Brian Fraser via RT"
I'd vote to first move it to the SQL::Statement queue and close it there -- |
Migrated from rt.perl.org#20858 (status was 'resolved')
Searchable as RT20858$
The text was updated successfully, but these errors were encountered: