Stas Bekman wrote:
> In any case, go ahead and commit your fix for now to get it working on
> OSX. we will figure out the special case posted by Dominique after 2.0.0
> is released. No point to keep on postponing the release date.
Allright, I still think that my patch is correctly fixing the probl
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>> Stas Bekman wrote:
>>
>>> Philippe M. Chiasson wrote:
>>> [...]
>>>
After a long promised investigation session, I believe I have pinned
it down. It seems to have been introduced by change r160562 when the
anon_cnt initialization
In any case, go ahead and commit your fix for now to get it working on
OSX. we will figure out the special case posted by Dominique after 2.0.0
is released. No point to keep on postponing the release date.
--
__
Stas Bekman
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
[...]
After a long promised investigation session, I believe I have pinned
it down. It seems to have been introduced by change r160562 when the
anon_cnt initialization code was moved around as a result. Didn't have
enough t
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> [...]
>
>> After a long promised investigation session, I believe I have pinned
>> it down. It seems to have been introduced by change r160562 when the
>> anon_cnt initialization code was moved around as a result. Didn't have
>> enough time tonigh
Philippe M. Chiasson wrote:
[...]
After a long promised investigation session, I believe I have pinned
it down. It seems to have been introduced by change r160562 when the
anon_cnt initialization code was moved around as a result. Didn't have
enough time tonight to dig down as to _why_ this is brea
Philippe M. Chiasson wrote:
After a long promised investigation session, I believe I have pinned
it down. It seems to have been introduced by change r160562 when the
anon_cnt initialization code was moved around as a result. Didn't have
enough time tonight to dig down as to _why_ this is breaking t
Christian Hansen wrote:
> Philippe M. Chiasson wrote:
>
>>
>> Just rebuilt myself a fresh blead-perl, fresh httpd-2.0-svn and
>> mod_perl-2.0-svn. All tests passed!
>>
>> My hunch is that's it's something about Apple's Perl, and I'll
>> investigate
>> more later on. For now, I guess the best advic
Philippe M. Chiasson wrote:
Just rebuilt myself a fresh blead-perl, fresh httpd-2.0-svn and
mod_perl-2.0-svn. All tests passed!
My hunch is that's it's something about Apple's Perl, and I'll investigate
more later on. For now, I guess the best advice is to try with a self-built
Perl and see if that
Stas Bekman wrote:
Christian, any difference if you test with perl w/o ithreads?
Yes, perl 5.8.6 compiled without ithreads works. perl 5.8.5 and 5.8.6
with ithreads fails.
Regards
Christian Hansen
Philippe M. Chiasson wrote:
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>>Christian Hansen wrote:
>>
>>
>>>Program received signal EXC_BAD_ACCESS, Could not access memory.
>>>0x014563fc in S_mess_alloc ()
>>>
>>>(gdb) bt
>>>#0 0x014563fc in S_mess_alloc ()
>>>#1 0x014566e8 in Perl_vmess (
Stas Bekman wrote:
> Christian Hansen wrote:
>
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> 0x014563fc in S_mess_alloc ()
>>
>> (gdb) bt
>> #0 0x014563fc in S_mess_alloc ()
>> #1 0x014566e8 in Perl_vmess ()
>> #2 0x014571dc in Perl_vcroak ()
>> #3 0x014576b8 in Perl_c
Stas Bekman wrote:
Christian Hansen wrote:
I'm using trunk, revision: 169956. With 1.999.21 all tests passes, so
guess something changed in the namespace change.
With the same perl and apache versions/configuration?
Yes exactly the same, i did a retest before submitting this report.
Christian, an
Christian Hansen wrote:
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x014563fc in S_mess_alloc ()
(gdb) bt
#0 0x014563fc in S_mess_alloc ()
#1 0x014566e8 in Perl_vmess ()
#2 0x014571dc in Perl_vcroak ()
#3 0x014576b8 in Perl_croak_nocontext ()
#4 0x007dd9c8 in modperl_glob
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x014563fc in S_mess_alloc ()
(gdb) bt
#0 0x014563fc in S_mess_alloc ()
#1 0x014566e8 in Perl_vmess ()
#2 0x014571dc in Perl_vcroak ()
#3 0x014576b8 in Perl_croak_nocontext ()
#4 0x007dd9c8 in modperl_global_cleanup ()
#5 0x006a
15 matches
Mail list logo
