Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Wez Furlong
There was a bugfix that wasn't merged from the 4.3 branch. Fixed in CVS now. --Wez. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread dv
> More info please... how big is a "certain size"? for me, the "certain size" is right at 12kb. 12,000 bytes es ok; 12,001 no es ok. i would trace/step if i knew how. > How about running "strace -e trace=net" ? > Even better, can you sit down and step through and find out where the > read is bei

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Wez Furlong
More info please... how big is a "certain size"? How about running "strace -e trace=net" ? Even better, can you sit down and step through and find out where the read is being cut short? The thing is that file_get_contents() should not have been sensitive to the greedy read problem (since it reads

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Red Wingate
works fine with the latest CVS-Snap for me php5-win32-200407121430.zip Win2K Apache2 -- red Curt Zirzow wrote: * Thus wrote Antony Dovgal: On Mon, 12 Jul 2004 15:00:09 + Curt Zirzow <[EMAIL PROTECTED]> wrote: * Thus wrote Andi Gutmans: When did you try that? Did you check with latest CVS beca

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Curt Zirzow
* Thus wrote Antony Dovgal: > On Mon, 12 Jul 2004 15:00:09 + > Curt Zirzow <[EMAIL PROTECTED]> wrote: > > > * Thus wrote Andi Gutmans: > > > When did you try that? Did you check with latest CVS because Wez > > > made some fixes. > > > > Just rechecked with current CVS version this morning and

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread dv
it's broken for me too using latest snap: php5-win32-200407121430 file_get_contents('http://php.net/'); > On Mon, 12 Jul 2004 15:00:09 + > Curt Zirzow <[EMAIL PROTECTED]> wrote: > >> * Thus wrote Andi Gutmans: >> > When did you try that? Did you check with latest CVS because Wez >> > made som

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Antony Dovgal
On Mon, 12 Jul 2004 15:00:09 + Curt Zirzow <[EMAIL PROTECTED]> wrote: > * Thus wrote Andi Gutmans: > > When did you try that? Did you check with latest CVS because Wez > > made some fixes. > > Just rechecked with current CVS version this morning and the > problem still persists. > > Not only

Re: [PHP-DEV] Re: Memory manager

2004-07-12 Thread Curt Zirzow
* Thus wrote Andi Gutmans: > When did you try that? Did you check with latest CVS because Wez made some > fixes. Just rechecked with current CVS version this morning and the problem still persists. Not only is it comming back with partial content, there seems to be blocks of ^@ chars between the

Re: [PHP-DEV] Re: Memory manager

2004-07-11 Thread Andi Gutmans
When did you try that? Did you check with latest CVS because Wez made some fixes. At 09:37 PM 7/11/2004 +, Curt Zirzow wrote: * Thus wrote Andi Gutmans: > I think I'll roll on Monday. There's still a patch lingering. > Does anyone else have something to commit? > This is completely broke: fil

Re: [PHP-DEV] Re: Memory manager

2004-07-09 Thread Daniel Convissor
Hi Andi: On Fri, Jul 09, 2004 at 03:19:43PM -0700, Andi Gutmans wrote: > I think I'll roll on Monday. There's still a patch lingering. > Does anyone else have something to commit? http://bugs.php.net/28999 please Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P

Re: [PHP-DEV] Re: Memory manager

2004-07-09 Thread Nuno Lopes
> I think I'll roll on Monday. There's still a patch lingering. > Does anyone else have something to commit? Hi Andi, Can you please waste just a minute reading one of my previous mail (that was lost in the middle of discussions), please? I need just an answer: bug or feature :-) Thanks, Nuno

Re: [PHP-DEV] Re: Memory manager

2004-07-09 Thread Andi Gutmans
I think I'll roll on Monday. There's still a patch lingering. Does anyone else have something to commit? At 09:58 AM 7/9/2004 +0200, Bert Slagter wrote: Andi Gutmans wrote: As I'd like to roll 5.0.0 by the end of the week, can developers please speak up if they have anything critical they are work