On 26.03.2009, at 01:30, Arnaud Le Blanc wrote:
On Wed, 2009-03-25 at 20:05 +0100, Lukas Kahwe Smith wrote:
On 19.03.2009, at 14:32, Arnaud Le Blanc wrote:
Hi,
After having seen some complaints about ticks being deprecated I'm
wondering if they could be un-deprecated for now.
Ticks are use
pleasure hearing from you Rasmus.
after observing lots of core dumps from apache, we got a different segfault and
its back trace is given bellow
#0 0x2aaab1c46688 in ZEND_FETCH_DIM_RW_SPEC_VAR_UNUSED_HANDLER (
execute_data=0x714ea6c8)
at /usr/local/src/php/php-5.2.9/Zend/zend_vm
Note that your backtrace doesn't touch PHP at all. It is entirely in
Apache land and it is a crash on a graceful shutdown.
-Rasmus
Rathnakar Konda wrote:
> Hi Guys,
>
> We are have a problem with apache segfault on our production server. Please
> read bellow for description.
>
> Its
> a web a
Hi Guys,
We are have a problem with apache segfault on our production server. Please
read bellow for description.
Its
a web application written in php5 and implemented most of the oop
concepts and lot of regular expressions, curl, mcrypt, simplexml,
mssql, exceptions and user defined error handl
http://docs.php.net/manual/en/intro.spl.php links to
http://www.php.net/~helly/php/ext/spl/ which does not reflect SPL in
5.3.
And since we have RC, more and more people start to test it and they
need newer docs.
I believe, that it's time to regenerate SPL's doxygen-docs.
p.s. let's skip holywars
Regeneration is really needed.
There've been a couple of changes in some classes.
Currently I'm using new added SplObjectStorage functionality and I
have to keep looking at source for available methods. Not a bad
thing... I'm feeling comfortable with C already, but some users may be
angry.
Cheer
On Thu, 26 Mar 2009, Alexey Zakhlestin wrote:
> p.s. let's skip holywars about "official" spl-docs. that's a separate
> topic.
I mentioned on twitter that proper docs would be useful too, let's see
if anybody writes to the doc list.
regards,
Derick
--
http://derickrethans.nl | http://ezcompo
2009/3/26 Alexey Zakhlestin :
> http://docs.php.net/manual/en/intro.spl.php links to
> http://www.php.net/~helly/php/ext/spl/ which does not reflect SPL in
> 5.3.
> And since we have RC, more and more people start to test it and they
> need newer docs.
>
> I believe, that it's time to regenerate SP
Rathnakar Konda wrote:
after observing lots of core dumps from apache, we got a different segfault and
its back trace is given bellow
#0 0x2aaab1c46688 in ZEND_FETCH_DIM_RW_SPEC_VAR_UNUSED_HANDLER (
execute_data=0x714ea6c8)
at /usr/local/src/php/php-5.2.9/Zend/zend_vm_execute.h
Jeremy wrote:
> Is there any way to access the parse tree of a PHP file from within PHP?
>
> I'm trying to write a code-checking utility to find namespace-related
> problems in code and alert me to them. Specifically:
>
> namespace foo\bar;
>
> function foobar()
> {
> try
> {
>
""William A. Rowe, Jr."" wrote in message
news:49cb613b.4070...@rowe-clan.net...
> Rathnakar Konda wrote:
>> after observing lots of core dumps from apache, we got a different
>> segfault and its back trace is given bellow
>>
>> #0 0x2aaab1c46688 in ZEND_FETCH_DIM_RW_SPEC_VAR_UNUSED_HANDLER
Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with
the other versions too):
- php.ini-development and php.ini-production parse error on line 581
- php_mcrypt.dll not present as a file in ./ext
- php_mhash.dll, php_msql.dll and php_pspell.dll are present as an
option in php.
hi,
On Thu, Mar 26, 2009 at 7:34 PM, Ionut G. Stan wrote:
> Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with the
> other versions too):
>
> - php.ini-development and php.ini-production parse error on line 581
Eric, can you look at it please?
> - php_mcrypt.dll not present
Hi Pierre and Ionut:
On Thu, Mar 26, 2009 at 07:40:04PM +0100, Pierre Joye wrote:
> On Thu, Mar 26, 2009 at 7:34 PM, Ionut G. Stan wrote:
> >
> > - php.ini-development and php.ini-production parse error on line 581
>
> Eric, can you look at it please?
That was fixed yesterday (per "php.ini-prod
On 3/26/2009 20:51, Daniel Convissor wrote:
That was fixed yesterday (per "php.ini-production& php.ini-development
last minute updates" thread).
Sorry, just saw it.
--
Ionut G. Stan
I'm under construction | http://igstan.blogspot.com/
--
PHP Internals - PHP Runtime Development Mailing
2009/3/26 Ionut G. Stan :
> On 3/26/2009 20:51, Daniel Convissor wrote:
>>
>> That was fixed yesterday (per "php.ini-production& php.ini-development
>> last minute updates" thread).
>>
>
> Sorry, just saw it.
Pierre just fixed the others except for phar in CVS, so the changes
will be in RC2 and t
Bringing this back to the list since its still relevant apparently.
On 26.03.2009, at 19:43, shire wrote:
Lukas Kahwe Smith wrote:
Also Marcus had some comments about your
"ZendEngine2/zend_language_scanner.c" change:
" thanks for looking into this. The patch looks pretty good for the
most
On Thu, 2009-03-26 at 11:38 +0100, Derick Rethans wrote:
> I mentioned on twitter that proper docs would be useful too, let's see
> if anybody writes to the doc list.
Just tell me what I need to do, and I will write the SPL docs
What format do they need to be in. What program is used to make the
On Thu, Mar 26, 2009 at 20:18, Kevin Waterson wrote:
> On Thu, 2009-03-26 at 11:38 +0100, Derick Rethans wrote:
>
>> I mentioned on twitter that proper docs would be useful too, let's see
>> if anybody writes to the doc list.
>
> Just tell me what I need to do, and I will write the SPL docs
> What
Hi Kevin
2009/3/26 Kevin Waterson :
> On Thu, 2009-03-26 at 11:38 +0100, Derick Rethans wrote:
>
>> I mentioned on twitter that proper docs would be useful too, let's see
>> if anybody writes to the doc list.
>
> Just tell me what I need to do, and I will write the SPL docs
> What format do they n
Lukas Kahwe Smith wrote:
Bringing this back to the list since its still relevant apparently.
On 26.03.2009, at 19:43, shire wrote:
There was another bug here http://bugs.php.net/bug.php?id=47596 that
is slightly related, I made an update in the comments. Dmitry just put
in a temporary fix so th
Hi Guys,
The Embed2 SAPI for embedded applications needing multi-thread enabled
PHP scripting support can be inspected from the following repository:
http://svn.tobin.nl/public/php/embed2/trunk/
The original Embedded SAPI does not allow concurrent script runs and
as such is less su
re,
To summarize:
On Thu, Mar 26, 2009 at 7:34 PM, Ionut G. Stan wrote:
> Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with the
> other versions too):
>
> - php.ini-development and php.ini-production parse error on line 581
fixed
> - php_mcrypt.dll not present as a file i
Hi all,
Brian, not sure if you're still trying to work on other scanner changes to
fix things, but wanted to say that I should have something (soon, whenever)
to fix the issues with \0 in strings/comments and/or YYFILL returning too
soon (maybe that's fixed, don't know). Basically, my idea is
Hey Matt,
Matt Wilmas wrote:
Hi all,
Brian, not sure if you're still trying to work on other scanner changes
to fix things, but wanted to say that I should have something (soon,
whenever) to fix the issues with \0 in strings/comments and/or YYFILL
returning too soon (maybe that's fixed, don't
Hi Dmitry,
I had looked at this Bug and wondering whether it should be fixed (I guess
the answer is yes :-)) and how to do so. I was only thinking along the
lines of adding a stack to keep track of multiple heredocs in the scanner.
Then I saw your fix and thought it was a cool method and bett
Pierre Joye wrote:
>> - php_phar.dll present as an option in php.ini but there is no need (causes
>> confusion)
>
> Will be change when we are sure of the built type (builtin or shared)
What is the debate? Whether windows build should match unix build?
Greg
--
PHP Internals - PHP Runtime Dev
Hi Greg
2009/3/27 Greg Beaver :
> Pierre Joye wrote:
>
>>> - php_phar.dll present as an option in php.ini but there is no need (causes
>>> confusion)
>>
>> Will be change when we are sure of the built type (builtin or shared)
>
> What is the debate? Whether windows build should match unix build?
Kalle Sommer Nielsen wrote:
> Hi Greg
>
> 2009/3/27 Greg Beaver :
>
>> Pierre Joye wrote:
>>
>>
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)
>>> Will be change when we are sure of the built type (builtin or shared)
>>>
Isn't it better to avoid any behaviour-changing #define's in a header
file? I mean the following series of lines in php_embed2.h:
/* we control char* lifetime of smart_str as we allow it to cross
request boundaries */
#define SMART_STR_USE_REALLOC 1
/* we use bigger numbers than default as script
On Thu, 2009-03-26 at 08:51 +0100, Lukas Kahwe Smith wrote:
> On 26.03.2009, at 01:30, Arnaud Le Blanc wrote:
>
> > On Wed, 2009-03-25 at 20:05 +0100, Lukas Kahwe Smith wrote:
> >> On 19.03.2009, at 14:32, Arnaud Le Blanc wrote:
> >>
> >>> Hi,
> >>>
> >>> After having seen some complaints about ti
31 matches
Mail list logo
