Steve Hay wrote:
[...]
One thought that I just about this stuff: I know that Linux users have
always been unable to reproduce this behaviour. Which malloc() are you
using? I'm using Perl's malloc() now (although admittedly I was using
the system malloc() before). If you're using the system m
Stas Bekman wrote:
>>OK, new patch attached. This compiles cleanly and fixes the perl-malloc
>>issues for me. Hope it's OK for you too.
>>
>>
>
>Almost there. env needs to be **env.
>
Oops. Yes, of course. Thanks.
- Steve
>Here is the patch that I've committed:
>
>Index: src/modules/pe
OK, new patch attached. This compiles cleanly and fixes the perl-malloc
issues for me. Hope it's OK for you too.
Almost there. env needs to be **env. Here is the patch that I've committed:
Index: src/modules/perl/mod_perl.c
===
---
Stas Bekman wrote:
>Steve Hay wrote:
>[...]
>
>
>>One thought that I just about this stuff: I know that Linux users have
>>always been unable to reproduce this behaviour. Which malloc() are you
>>using? I'm using Perl's malloc() now (although admittedly I was using
>>the system malloc() be
The mp2 test suite contains a test for Apache::Reload, but it doesn't
seem to test unloading a modules with an XS component, unless I'm
missing something.
Applying the attached changes alters the test so that instead of
unloading the tiny pure-Perl Apache::Reload::Test module, it now tries
to
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>
>>>Index: src/modules/perl/mod_perl.c
>>>===
>>>--- src/modules/perl/mod_perl.c (revision 151089)
>>>+++ src/modules/perl/mod_perl.c (working copy)
>>>@@ -544,9 +544,9 @@
>>>{
>>>
