Date: 08/30/00
- Next message: Andi Gutmans: "[PHP-DEV] ENFORCE_SAFE_MODE"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #6096 Updated: Script causes segfault"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] Changing opened_path to being emalloc()'ed"
- Reply: Zeev Suraski: "Re: [PHP-DEV] Changing opened_path to being emalloc()'ed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
Something which has been on my TODO for a loooooong time but I didn't do it
because I wanted to wait for after 4.0.2.
Does anyone see any reason for opened_path not to be emalloc()'ed? It's
been like this for historic reasons and I haven't seen opened_path being
used neither before nor after our memory manager is initialized/shutdown.
So I want to change it all to emalloc()'s now so that we don't have leaks.
Andi
--- Andi Gutmans <andi <email protected>> http://www.zend.com/-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Andi Gutmans: "[PHP-DEV] ENFORCE_SAFE_MODE"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #6096 Updated: Script causes segfault"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] Changing opened_path to being emalloc()'ed"
- Reply: Zeev Suraski: "Re: [PHP-DEV] Changing opened_path to being emalloc()'ed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

