John Unsworth wrote:
> Thanks.
>
> However that is still dangerous. Someone could build perl to use perl memory
> manager even if the platform isn't windows
Yes, which is something I've always done without ill-effect. The perl
dist that comes with the distribution that I run has PERL_MALLOC
ena
: 20 July 2007 20:42
To: ARSperl User Discussion
Subject: Re: [Arsperl-users] ars_CreateEntry crashing on Windows
John Unsworth wrote:
> Hello,
>
> Can someone explain what happens now? Do we get notified of an
> official fix?
>
I added this patch to the CVS tree. Since the
John Unsworth wrote:
> Hello,
>
> Can someone explain what happens now? Do we get notified of an official fix?
>
I added this patch to the CVS tree. Since the discussion centered around
the bug affecting Windows, I modified the suggested fix to be:
> /* malloc that will never return null */
>
perl-users] ars_CreateEntry crashing on Windows
We have fixed this by the following change to mallocnn in support.c.
/* malloc that will never return null */
void *
mallocnn(int s)
{
#ifdef malloc
#undef malloc
#endif
void *m = malloc(s ? s : 1);
if (!m)
We have fixed this by the following change to mallocnn in support.c.
/* malloc that will never return null */
void *
mallocnn(int s)
{
#ifdef malloc
#undef malloc
#endif
void *m = malloc(s ? s : 1);
if (!m)
croak("can't malloc");
mems
5 matches
Mail list logo
