dl() is evil!
This is a bug which most likely will never be resolved (except for nuking
dl()).
Andi
At 04:19 PM 10/22/2001 -0700, Rasmus Lerdorf wrote:
An update to this. It only happens if an extension is dl()'ed. If it is
loaded via an extension= in php.ini it works fine.
-Rasmus
On Mon,
On Thu, Oct 25, 2001 at 06:50:10PM +0200, Andi Gutmans wrote :
dl() is evil!
This is a bug which most likely will never be resolved (except for nuking
dl()).
Can you elaborate more? Technically?
- Markus
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL
Look up in the archives... Basically if there are any leaks in emalloc()'d
data that was loaded in a dynamic module, memory blocks will be pointing at
addresses which no longer exist if we're in debug mode (the __FILE__ stuff).
Zeev
At 00:58 26/10/2001, Markus Fischer wrote:
On Thu, Oct 25,
The leak notices and other --enable-debug messages seem to be brokwn right
now.
ie.
stick a stray char *s = emalloc(20); somewhere and try running php
script.php from the command line. I get a segfault that looks like this:
#0 0x406ab75c in _IO_vfprintf (s=0xbfffeca0, format=0x8186e40 %s(%d)
An update to this. It only happens if an extension is dl()'ed. If it is
loaded via an extension= in php.ini it works fine.
-Rasmus
On Mon, 22 Oct 2001, Rasmus Lerdorf wrote:
The leak notices and other --enable-debug messages seem to be brokwn right
now.
ie.
stick a stray char *s =
It's a very old bug, it even has an open entry in the bugs
database. Haven't thought of a good solution for it...
At 01:19 23-10-01, Rasmus Lerdorf wrote:
An update to this. It only happens if an extension is dl()'ed. If it is
loaded via an extension= in php.ini it works fine.
-Rasmus
On
Me; but the segfault is only visible on win32. Hah; and I thought
it was my fault ? (it probably is anyway ;)
- Markus
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list
