Re: PHP 4.0 Bug #7720 Updated: Return address instackoverwritten?

Only *nix systems have dynamic stacks, windows based programs live with a fixed size stack setup at compile time (last time I did win coding, anyway :). There are many other ways of dealing with a recursive situation that won't involved you running out. Either way, to far OT now for my tastes. Its not a real 'bug', live with it. adamw ----- Original Message ----- From: "void" <sven@devcon.net> To: "Adam Wright" <adam@elysium.ltd.uk> Cc: "PHP Development" <php-dev@lists.php.net> Sent: Thursday, November 09, 2000 12:57 PM Subject: Re: [PHP-DEV] PHP 4.0 Bug #7720 Updated: Return address instackoverwritten? > On Thu, 9 Nov 2000, Adam Wright wrote: > > > Date: Thu, 9 Nov 2000 12:54:54 -0000 > > From: Adam Wright <adam@elysium.ltd.uk> > > To: PHP Development <php-dev@lists.php.net> > > Subject: Re: [PHP-DEV] PHP 4.0 Bug #7720 Updated: Return address in > > stackoverwritten? > > > > in C, and marvel as you run out of stack. This isnt a bug in PHP, though its > > not handled that gracefully. 10,000 recursions is an awful lot anyway, and > > you should look at other methods to accomplish your goal (think of the > > memory usage even if you had enough stack!), imho. > > Yeah, right, it's a lot. In C the stack just grows and everyone is > happy when just memory runs out. php instead overwrites a return > address on the stack. We found this problem in many other exploits > before. > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > >