I am not seeing this problem with Apache 1.3, PHP_4_3 or php5-HEAD and
tru64, nor with the cli.
What platform are you seeing it on ? Could it be any unitilized or buffer
overflow issue ?
Dave
- Original Message -
From: "Sebastian Bergmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent:
> It should be a runtime or compiletime flag in each extension, not a
> seperate text file that someone needs to read.
In a truely perfect world we would have that compile time flag in the
extension definition structure, and then could do a extension specific
lock (mutex) before calling functions
Hi,
back on reentrancy I know that with some of the libraries the extensions
depend on are not reentrant (ie. also not thread safe). The imap library cclient comes
to mind (unless something has changed recently) and I know gettext caches data in
global structures (which would make me wo
Hi all,
while trying to understand a test failure on Tru64 I noticed that
ext/standard/parsedate.y is not reentrant. I am assuming that we do care
about this given the effort with ZTS and I care because I build Apache2
multithreaded.
I am not much of a bison expert (other than to say that
I need to change the US/Eastern references as well - needs to be EST5
or EST-5.
Dave
- Original Message -
From: "Marcus Börger" <[EMAIL PROTECTED]>
To: "David Hill (php.net)" <[EMAIL PROTECTED]>
Cc: "Php-Qa" <[EMAIL PROTECTED]>; <[EMA
> I have found some problems (and possible solutions) concerning use
of the
> gettext extension on multithreaded servers.
The gettext library caches information in static variables. This
is true in gettext 0.10.40 at least, which is that last that I looked
in. This has a number of "features"
Hi all,
It would seem that Tru64 is pickier about the TZ setting than the rest of the
known universe. According to our local TZ expert (who can quote chapter and verse from
the UNIX 98 standard) a TZ of GMT is not proper, and GMT0 is (again despite the fact
that every other platform seems to
> Some 64bit issues, some bugs marked "Critical", etc..
>
On the 64bit issues... other than the ext/mbstring thing I am not
currently aware of any. I am still looking at the current test
failures though - I have 12 and so far 3 are explainable do to os
"features" and one is the mbstring pro
yo,
I was trying to build php5 - head and got a syntax error in config. After some
brute force wacking, I narrowed it down to ext/mysqli/config.m4.
Not being very conversant with automake I don't really see anything wrong with the
file. and as it is not in PHP_4_3 I don't have anyth
