On 9/15/15 5:15 PM, Michael Schout wrote:
> Reverting the change to op.c completely fixes the problem. I cannot
> reproduce the panic after this change, and I do not get any segmentation
> faults either in a large codebase that I am also testing against.
I should have mentioned I reverted the ch
As reported in other thread, I've seen mod_perl emit panic warnings such
as the following ever since 5.19.7:
panic: attempt to copy freed scalar 7fb2264ffde0 to 7fb2264ffd08 at
/Users/mschout/Sync/Apache-TryCatch/blib/lib/Apache/TryCatch.pm line 20.
I've also seen random segementation faults cau
First, let me thank you for your efforts! I doubt I could have come to the
bottom of that. Unfortunately, I have been unable to reproduce my problem
outside of a production environment and I can't risk pushing a version of
perl into production that I've built myself just to test that. As unhelpful
Steve, John:
I did a bisect today against perl git, using mod_perl 2.0.9 and apache
2.2.29 to find out where my two issues were caused. It turns out that
both of my problems, which were:
- panic: attempt to copy freed scalar to
and also
- segmentation fault caused by a specific "retu
