On Sun, 2003-08-31 at 06:18, Andi Gutmans wrote:
[...libxml2 requirements...]
> > I can add that..but shouldn't we just go ahead and require
> > 2.5.9 or greater instead of skipping ONE version??
>
> I think that's probably a good idea although it might piss some people off :)
Just FYI, I
From: Jani Taskinen
> And do you really want to hunt after all ghost bugs that are really
> caused by buggy libxml versions..? And like you said, PHP 5 is still
> beta. Nobody should be using it for real anyway. :)
>
> (and they can always do '--disable-xml' etc.)
>
> So I say w
At 14:01 31/08/2003, Rob Richards wrote:
From: Jani Taskinen
> And do you really want to hunt after all ghost bugs that are really
> caused by buggy libxml versions..? And like you said, PHP 5 is still
> beta. Nobody should be using it for real anyway. :)
>
> (and they can always do
On Sun, 31 Aug 2003, Rob Richards wrote:
>From: Andi Gutmans
>
>> > I can add that..but shouldn't we just go ahead and require
>> > 2.5.9 or greater instead of skipping ONE version??
>>
>> I think that's probably a good idea although it might piss some people off
>:)
>
>Since this is still
On Sun, 31 Aug 2003, Rob Richards wrote:
>From: Andi Gutmans
>
>> > I can add that..but shouldn't we just go ahead and require
>> > 2.5.9 or greater instead of skipping ONE version??
>>
>> I think that's probably a good idea although it might piss some people off
>:)
>
>Since this is still
From: Andi Gutmans
> > I can add that..but shouldn't we just go ahead and require
> > 2.5.9 or greater instead of skipping ONE version??
>
> I think that's probably a good idea although it might piss some people off
:)
Since this is still a beta why not just skip that one version. 2.5.4 i
At 12:59 AM 8/31/2003 +0300, Jani Taskinen wrote:
On Sat, 30 Aug 2003, Andi Gutmans wrote:
>>If so, then libxml 2.5.8 would have to be marked bad unless you can also
>>know when the other mods call their cleanup. This is a 2.5.8 issue only as
>>it was introduce in that version and fixed in 2.5.9.
On Sat, 30 Aug 2003, Andi Gutmans wrote:
>>If so, then libxml 2.5.8 would have to be marked bad unless you can also
>>know when the other mods call their cleanup. This is a 2.5.8 issue only as
>>it was introduce in that version and fixed in 2.5.9.
>
>Can someone who knows configure well please add
At 09:56 AM 8/30/2003 -0400, Rob Richards wrote:
From: Andi Gutmans
> Ouch. Now the question is how do we solve this? Do we make ./configure
bail
> out on such versions or do we hack something into PHP so that it doesn't
> call this function more than once?
> I really want to reduce the block size
From: Andi Gutmans
> Ouch. Now the question is how do we solve this? Do we make ./configure
bail
> out on such versions or do we hack something into PHP so that it doesn't
> call this function more than once?
> I really want to reduce the block size in my mem manager from 256KB to
16KB
> but I can'
At 03:09 PM 8/30/2003 +0200, Thies C. Arntzen wrote:
you are likely to have a buggy version of libXml, that
causes this when xmlCleanupParser is called more than once.
this happens if two php-modules use libXml and call
xmlCleanupParser in the [R|M]SHUTDOWN
Ouch. Now the question i
On Sat, Aug 30, 2003 at 04:05:42PM +0300, Andi Gutmans wrote:
> Hi,
>
> I've been debugging a problem with my memory manager for quite a while (I
> was playing with different block sizes) when I discovered there doesn't
> seem to be a bug but the heap gets corrupted by some other place in PHP. I
Hi,
I've been debugging a problem with my memory manager for quite a while (I
was playing with different block sizes) when I discovered there doesn't
seem to be a bug but the heap gets corrupted by some other place in PHP. It
just happens that the memory manager makes this problem appear sooner
13 matches
Mail list logo
