Front page | perl.perl5.porters |
Postings from May 2013
On Tue, May 07, 2013 at 06:52:45PM -0600, Karl Williamson wrote:
> On 05/07/2013 06:44 PM, Karl Williamson wrote:
> >On 05/07/2013 07:17 AM, Mark Phillips via RT wrote:
> >>What is the status of this bug?
> >>Any chance of getting it fixed because it is painful having to rebuild
> >>perl every time redhat ships another broken version:-)
> >>
> >
> >As another data point, I get this:
> >ยง myperl test.pl
> >HUP
> >HUP
> >panic: sv_chop ptr=9486829, start=9494518, end=9494528 at test.pl line 13.
> >
> >(In repeated runs)
> >
>
> I forgot to mention that myperl means blead.
>
> And, in 5.16.0, there is no panic, but there is the bug stated in
> the ticket.
Just to confirm what you are saying: that the OP's bug report code on
your *blead* causes the panic shown above?
If so, that's a new kettle of fish. The original assumption had been
that the bug was fixed in blead, and the discussion was merely about
backporting a modified version of the "fixing" commit to maint-5.14 and
maint-5.16.
FWIW, I can't reproduce any failures on blead.
What are the commit and the build options for your blead?
--
The Enterprise is captured by a vastly superior alien intelligence which
does not put them on trial.
-- Things That Never Happen in "Star Trek" #10
Thread Previous
|
Thread Next