Re: http://bugs.php.net/bugs.php?id=2220

From: Date: Sun, 11 Jun 2000 19:08:18 +0000
Subject: Re: http://bugs.php.net/bugs.php?id=2220
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-21047@lists.php.net to get a copy of this message
More seriously - it shouldn't be a problem to have PHP_COMPILE_DL #define'd when compiling a dynamic module, should it? Zeev On Sun, 11 Jun 2000, Zeev Suraski wrote: > On Sun, 11 Jun 2000, Sascha Schumann wrote: > > > On Sun, 11 Jun 2000, Zeev Suraski wrote: > > > > > On Sun, 11 Jun 2000, Sascha Schumann wrote: > > > > > > > On Sun, 11 Jun 2000, Zeev Suraski wrote: > > > > > > > > > > > > > > This is an old report for the leak/dl() bug that came up a few days ago. > > > > > > > > > > Sascha - unless I'm mistaken, there's no longer a generic way of > > > > > finding > > > > > whether we're during a compilation of a dynamic module, right? > > > > > > > > In what context? In the source files or where? > > > > > > Yes. We'd have to #define the _emalloc() macro to somehow avoid keeping > > > static references to __FILE__ if we're compiling a dynamically loadable > > > module. > > > > How about simply strdup'ing the strings, so that you don't > > keep any static references at all? > > Yeah well, that's how it used to be, but it's a serious slowdown; > Otherwise, ZEND_DEBUG doesn't add a significant overhead. > > Perhaps it's a good incentive for module authors not to have leaks :) > > Zeev > > -- Zeev Suraski <zeev@zend.com> http://www.zend.com/

« previous php.dev (#21047) next »