On Apr 3, 2006, at 9:26 PM, Christian Stocker wrote:
On 4.4.2006 3:40 Uhr, Andrei Zmievski wrote:
The problem is that SHLIB_SUFFIX_NAME is used for both bundles
(.so) and dynamic libraries (.dylib) on Mac OS X. These are
separate entities and need to be treated separately. We could
probabl
I prefer (2) or (3).
(3) requires less changes.
#define S_DUPLICATE (1<<0)
#define S_AUTO_FREE (1<<1)
#define ZVAL_U_STRINGL(conv, z, s, l, flags) \
if (UG(unicode)) { \
UErrorCode status = U_ZERO_ERROR; \
UChar *u_str; \
int u_len; \
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (622 total including feature requests)
===[*Configuration Issues]
36257 Open php ini master values are reset between vhosts
==
On 4.4.2006 3:40 Uhr, Andrei Zmievski wrote:
The problem is that SHLIB_SUFFIX_NAME is used for both bundles (.so) and
dynamic libraries (.dylib) on Mac OS X. These are separate entities and
need to be treated separately. We could probably set SHLIB_SUFFIX_NAME
to .dylib on OSX and introduce a
The problem is that SHLIB_SUFFIX_NAME is used for both bundles (.so)
and dynamic libraries (.dylib) on Mac OS X. These are separate
entities and need to be treated separately. We could probably set
SHLIB_SUFFIX_NAME to .dylib on OSX and introduce an additional
variable, something like BUNDL
duplicate should only ever be set to 0 on this (or any of the
macros) when
the string *is* allocated with emalloc. Otherwise the
enegine would get in
trouble freeing it later on.
No. :(
You can use ZVAL_RT_STRING(&fname, "strlen", 0), then call
zend_call_function(&fname) and do not destroy fnam
Hi Sara,
> -Original Message-
> From: Sara Golemon [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 9:03 PM
> To: "Dmitry Stogov"
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] RETURN_RT_STRING() and family leakage
>
>
> > Your first solution will not work. String passed
Your first solution will not work. String passed to
ZVAL_RETURN_RT_STRING()
may be not allocated by emalloc().
duplicate should only ever be set to 0 on this (or any of the macros) when
the string *is* allocated with emalloc. Otherwise the enegine would get in
trouble freeing it later on. I
Hi,
Karoly Negyesi a écrit :
> > Please note that the only difference between f1 and f2 that the first
> > records the return value of f3() into a variable. However, this
> > changes the output:
> >
> > array(1) {
> > ["foo"]=>
> > &string(3) "bar"
> > }
> > array(1) {
> > ["foo"]=>
> > s
Hi Sara,
Your first solution will not work. String passed to ZVAL_RETURN_RT_STRING()
may be not allocated by emalloc().
The second solution will work.
ZVAL_RETURN_RT_STRINGL(str, len, duplicate) -> ZVAL_RETURN_RT_STRINGL(str,
len, duplicate, auto_free)
3) It is possible to reuse "duplicate" arg
Hello,
I would like to see a patch for current overloading function memory
fragmentations with segfault before release. See bug #36647.
As far as I know Dmitry is looking at it.
Thanks,
mike
Ilia Alshanetsky wrote:
PHP 5.1.3RC2 has just been released, about a week late, but better
late then
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (491 total including feature requests)
===[*Compile Issues]==
36404 Open configure script cannot complete libxml build
===
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (635 total including feature requests)
===[*Configuration Issues]
36257 Open php ini master values are reset between vhosts
==
13 matches
Mail list logo
