On 29 October 2013 11:52, Jan Kaluža <jkal...@redhat.com> wrote:
> On 10/28/2013 10:05 AM, Steve Hay wrote:
>>
>> On 4 October 2013 18:04, Steve Hay <steve.m....@googlemail.com> wrote:
>>>
>>> I've tried the current httpd24 branch with Apache Lounge's 2.4.6 and
>>> my own build of Perl 5.19.4. The build works fine but the test suite
>>> crashes httpd.exe in t/api/add_config.t ("free from wrong pool"),
>>> which I'm sure was not happening for me previously.
>>
>>
>> I've been looking more at this but haven't figured it out yet.
>>
>> Debugging the test server processing the URL
>> http://localhost:8562/TestAPI__add_config/, I find that it crashes in
>> modperl_cleanup_pnotes() - in Safefree() on the first call to
>> Perl_hv_undef_flags():
>>
>>          if (header->interpreter != aTHX) {
>>          Perl_croak_nocontext("panic: free from wrong pool, %p!=%p",
>>                       header->interpreter, aTHX);
>>          }
>>
>> The header->interpreter is the value saved away in cleanup_data->perl
>> by modperl_pnotes_cleanup_data(), which is registered as the cleanup
>> routine when the pnotes is made in modperl_pnotes(), so that's been
>> correctly restored to aTHX in modperl_cleanup_pnotes(), but the aTHX
>> in Safefree() is different and I don't know why, or how this was
>> working before :-/
>>
>
> Hm, I have no idea what's going on here, but it does not happen for me with
> older Perl. The good thing is that Fedora 20 just updated to Perl-5.18, so I
> will try to install F20 and Perl-5.18 and give it a try. Will write you soon
> how it worked.
>

I've just tried a couple more random (older) perls and have found that
it fails with 5.19.1 and 5.18.0 too, but works with 5.16.0.

However, I suspect the difference is the build configuration rather
than the version. That 5.16.0 has PERL_IMPLICIT_SYS disabled...

I will try current perls with that disabled, and older perls with it
enabled to check this out, but I'm already feeling like that's likely
to be the culprit.

I wonder if it would be worth getting the threading branch merged into
trunk and then update the 2.4 branch from trunk, so as to pull in
those threading fixes -- they might well sort this out. I'll start a
new thread (heh!...) to enquire about the status of that other branch.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org
For additional commands, e-mail: dev-h...@perl.apache.org

Reply via email to