[snip]
> That worked fine. I am sure that there are many differences in our
> environments. We are running Suse Linux, PHP 5.2.1, Apache 2.2.4.
That's close though - my workstation is openSUSE 10.2, PHP 5.2.4, Apache
2.2.4.
[/snip]
As this installation is on a development box it has nearly every
Jay Blanchard wrote:
> [snip]
> I'm on Linux too, so never mind Windows for the moment.
> So what's the difference between our two environments? Try putting
> something in the problem-include file to verify that virtual is doing
> what it's supposed to.
> [/snip]
>
> That worked fine. I am sure
[snip]
I'm on Linux too, so never mind Windows for the moment.
So what's the difference between our two environments? Try putting
something in the problem-include file to verify that virtual is doing
what it's supposed to.
[/snip]
That worked fine. I am sure that there are many differences in
Jay Blanchard wrote:
>> [snip]
>> You are right. It segfaults only if the virtual() call comes before
>> creating the XSLTProcessor instance.
>> [/snip]
>>
>> I cannot replicate the problem on Linux.
>>
>
> So you get the XSLT error messages instead? That's what you should be
> seeing.
> {/sni
Jay Blanchard wrote:
> [snip]
> A core dump or an strace or some debug output at the right time will
> have 99% of the information you need - provided you understand how to
> read it.
> I submit there is generally no need to reproduce a problem in order to
> diagnose it. To fix it, yes, it will u
T.Lensselink wrote:
> In one of the other messages i stated the script works fine on linux.
> But PHP on windows seems to have a problem with virtual(). Even
> without creating an instance of the XSLProcessor class.
>
> But dropping virtual() for include() or require() solves the problem.
Gettin
On Fri, 14 Sep 2007 08:10:56 -0500, "Jay Blanchard" <[EMAIL PROTECTED]>
wrote:
> [snip]
> You are right. It segfaults only if the virtual() call comes before
> creating the XSLTProcessor instance.
> [/snip]
>
> I cannot replicate the problem on Linux.
>
> --
> PHP General Mailing List (http://
> [snip]
> You are right. It segfaults only if the virtual() call comes before
> creating the XSLTProcessor instance.
> [/snip]
>
> I cannot replicate the problem on Linux.
>
So you get the XSLT error messages instead? That's what you should be
seeing.
{/snip]
Yep, no segfault. I do not have
Jay Blanchard wrote:
> [snip]
> You are right. It segfaults only if the virtual() call comes before
> creating the XSLTProcessor instance.
> [/snip]
>
> I cannot replicate the problem on Linux.
>
So you get the XSLT error messages instead? That's what you should be
seeing.
See also http://bu
[snip]
You are right. It segfaults only if the virtual() call comes before
creating the XSLTProcessor instance.
[/snip]
I cannot replicate the problem on Linux.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
T.Lensselink wrote:
>>> Would love to see the code that caused this.
>>
>> http://jessen.ch/files/php-problem-sep2007.tar.gz
>>
>>
>> /Per Jessen, Zürich
>>
>> --
>> PHP General Mailing List (http://www.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>
> Don't really see what
On Fri, 14 Sep 2007 12:00:19 +0200, Per Jessen <[EMAIL PROTECTED]> wrote:
> T.Lensselink wrote:
>
Would love to see the code that caused this.
>>>
>>> http://jessen.ch/files/php-problem-sep2007.tar.gz
>>>
>>>
>>> /Per Jessen, Zürich
>>>
>>> --
>>> PHP General Mailing List (http://www.php.
T.Lensselink wrote:
>>> Would love to see the code that caused this.
>>
>> http://jessen.ch/files/php-problem-sep2007.tar.gz
>>
>>
>> /Per Jessen, Zürich
>>
>> --
>> PHP General Mailing List (http://www.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>
> It's the call to virt
Stut wrote:
> Per Jessen wrote:
>>> Segfaults are a fact of life
>>
>> Only if you are forced to accept poor programming. I can assure you
>> that segfaults are not tolerated in a regular production environment.
>> Segfaults happen in test and development.
>
> I agree with you for the most part
On Fri, 14 Sep 2007 11:09:36 +0200, Per Jessen <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
>> On Fri, 14 Sep 2007 10:10:09 +0200, Per Jessen <[EMAIL PROTECTED]>
>> wrote:
>>> Per Jessen wrote:
>>>
To let a user script bring down the host environment is just not
acceptable. I
On Fri, 14 Sep 2007 11:09:36 +0200, Per Jessen <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
>> On Fri, 14 Sep 2007 10:10:09 +0200, Per Jessen <[EMAIL PROTECTED]>
>> wrote:
>>> Per Jessen wrote:
>>>
To let a user script bring down the host environment is just not
acceptable. I
Per Jessen wrote:
Segfaults are a fact of life
Only if you are forced to accept poor programming. I can assure you
that segfaults are not tolerated in a regular production environment.
Segfaults happen in test and development.
I agree with you for the most part, but there are several point
[EMAIL PROTECTED] wrote:
> On Fri, 14 Sep 2007 10:10:09 +0200, Per Jessen <[EMAIL PROTECTED]>
> wrote:
>> Per Jessen wrote:
>>
>>> To let a user script bring down the host environment is just not
>>> acceptable. IMHO.
>>
>> Here's an example from this morning - I have a situation where all I
>>
On Fri, 14 Sep 2007 10:10:09 +0200, Per Jessen <[EMAIL PROTECTED]> wrote:
> Per Jessen wrote:
>
>> To let a user script bring down the host environment is just not
>> acceptable. IMHO.
>
> Here's an example from this morning - I have a situation where all I
> need to do is add a single superfluou
Per Jessen wrote:
> To let a user script bring down the host environment is just not
> acceptable. IMHO.
Here's an example from this morning - I have a situation where all I
need to do is add a single superfluous double quote, and I get a
segfault. Is that not poor error handling somewhere?
Stut wrote:
> Please tell me you're kidding? If you can't provide a piece of code
> that always causes the segfault are you seriously expecting the devs
> to waste their time trying to find the cause? Talk about a needle in a
> haystack.
>
> The ease of reproduction is not particularly important,
[snip]
I beg to differ. In the past 20 years, I've spent plenty of time
working with core dumps, stand-alone dumps, slip traps and system
traces debugging my own software (running at customer sites) without
the remotest possibility of reproducing a problem on-demand.
If you think a problem must be
Per Jessen wrote:
Stut wrote:
Anyway, I think it's exceptionally poor show by php to cause a
segfault, probably due to user code. I know it does it every now and
then, and nobody has ever been interested in looking at the core
dump.
This will have nothing to do with user code since no user co
Zbigniew Szalbot wrote:
> Problem solved! Daniel - this really helped. I do not even know how to
> thank you but surely, this is amazing. This thing actually works! :)
Amazing indeed. PHP does good work for me, but I'm not impressed.
/Per Jessen, Zürich
--
PHP General Mailing List (http://ww
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Hello,
>
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > No problem at all.
>
> Your help was very much appreciated!
>
> >
> > Now my guess at explaining it
> >
> > Notice how `IfModule mod_php5.c` if only mentioned when n
Jay Blanchard wrote:
>> Whenever I've reported a core-dump (which I've stopped doing),
>> nothing's been done about it unless I've been able to produce a short
>> script to reproduce.
>> [/snip]
>
> That is to be expected and is standard operating procedure for any
> development team.
I beg to
Zbigniew Szalbot wrote:
> It is clearly problem with indexes but how and where that is an issue
> for me. there is a solution which I could live with. That is I can
> create an index.html page which will simply redirect to index.php and
> so index-wise everything will work but I would really prefe
Hello,
2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> No problem at all.
Your help was very much appreciated!
>
> Now my guess at explaining it
>
> Notice how `IfModule mod_php5.c` if only mentioned when nested
> inside of the `IfModule mod_php3.c` container. If you want to have
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Dear Daniel and all!
>
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > DirectoryIndex index.php index.php3 index.html
> > > > > > > >
> > > >
Dear Daniel and all!
2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > DirectoryIndex index.php index.php3 index.html
> > > > > > >
> > > > > > >
> > > > > > > DirectoryIndex index.php index
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Hello,
>
> 2007/9/12, Zbigniew Szalbot <[EMAIL PROTECTED]>:
> > Hello again,
> >
> > 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > > >
> > > > > >
> > > > > >
> > > > > > DirectoryIndex index.php index.php3
Hello,
2007/9/12, Zbigniew Szalbot <[EMAIL PROTECTED]>:
> Hello again,
>
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > >
> > > > >
> > > > >
> > > > > DirectoryIndex index.php index.php3 index.html
> > > > >
> > > > >
> > > > > Dire
Hello again,
2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > >
> > > >
> > > >
> > > > DirectoryIndex index.php index.php3 index.html
> > > >
> > > >
> > > > DirectoryIndex index.php index.php3 index.html
> > > >
> > > >
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Hello,
>
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > > >
can i ask why you have anything to do with mod_php3 there?
and if you don't plan on trying to use php4 and php5, then remove any
looking for php4 too.
> >
> >
> >
> > DirectoryIndex index.php index.php3 index.html
> >
> >
> > DirectoryIndex
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Hello,
>
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > > >
Hello,
2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > > There's only one problem left to be solved. After the upgrade php
> >
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> 2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> > On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > > There's only one problem left to be solved. After the upgrade php
> > > scripts behave as if they were not recognized. I made a te
2007/9/12, Daniel Brown <[EMAIL PROTECTED]>:
> On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> > There's only one problem left to be solved. After the upgrade php
> > scripts behave as if they were not recognized. I made a test and put a
> > standard index.html file in a directory, called
On 9/12/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> There's only one problem left to be solved. After the upgrade php
> scripts behave as if they were not recognized. I made a test and put a
> standard index.html file in a directory, called a browser and the page
> was displayed properly. I t
Dear all,
2007/9/12, Lester Caine <[EMAIL PROTECTED]>:
> Per Jessen wrote:
> >>> Maybe it's worth doing some googling for wordpress and php5? If it's
> >>> not your code, it's not easy to debug. I have seen the apache core
> >>> dump many times, sometimes caused by obvious errors, other times by
[snip]
> [snip]
> Anyway, I think it's exceptionally poor show by php to cause a
> segfault,
> probably due to user code. I know it does it every now and then, and
> nobody has ever been interested in looking at the core dump.
> [/snip]
>
> The Dev team looks at core dumps all of the time to try
Jay Blanchard wrote:
> [snip]
> Anyway, I think it's exceptionally poor show by php to cause a
> segfault,
> probably due to user code. I know it does it every now and then, and
> nobody has ever been interested in looking at the core dump.
> [/snip]
>
> The Dev team looks at core dumps all of t
Stut wrote:
>> Anyway, I think it's exceptionally poor show by php to cause a
>> segfault, probably due to user code. I know it does it every now and
>> then, and nobody has ever been interested in looking at the core
>> dump.
>
> This will have nothing to do with user code since no user code is
On 9/12/07, Per Jessen <[EMAIL PROTECTED]> wrote:
> Sorry, I have to disagree strongly here. I have seen apache core dump
> many times due to PHP user code. I've also opened bug-reports based on
> such core-dumps, but the PHP developer community is not
> interested/capable in debugging in that fa
Lester Caine wrote:
>> Anyway, I think it's exceptionally poor show by php to cause a
>> segfault,
>> probably due to user code. I know it does it every now and then, and
>> nobody has ever been interested in looking at the core dump.
>
> Zbigniew has not actually managed to get Apache started w
Daniel Brown wrote:
> On 9/12/07, Per Jessen <[EMAIL PROTECTED]> wrote:
>> Migrating from v4 to v5 is not necessarily straight forward.
>> Depending on what features you've used, you may have to rewrite some
>> of
>> your code. For instance, we used the xslt sablotron interface, which
>> no longe
Per Jessen wrote:
Maybe it's worth doing some googling for wordpress and php5? If it's
not your code, it's not easy to debug. I have seen the apache core
dump many times, sometimes caused by obvious errors, other times by
something obscure and difficult to find.
Come on guys, use your heads. P
I have the same problem with PHP-5.2.3 on my freebsd 6.2. After commenting
recode, sockets, ming, sysvshm modules, there were no more core dumps. So,
you have to comment the sockets modules in extension.ini and everything will
work fine.
Jon Anderson wrote:
If the version of PHP you're using is a binary package, you should
probably generate a backtrace from the core that was dumped and report
it as a bug to the provider of that binary. The same goes if it was
built as a FreeBSD port - they should probably know that their defaul
Per Jessen wrote:
Stut wrote:
Hi Zbigniew
Maybe it's worth doing some googling for wordpress and php5? If it's
not your code, it's not easy to debug. I have seen the apache core
dump many times, sometimes caused by obvious errors, other times by
something obscure and difficult to find.
Come
Per Jessen wrote:
Uh, how do know you it's do with the version-number?? Did I miss that
posting?
Not necessarily to do with the version number itself - it's that PHP is
dying before having actually done anything - it never gets to any PHP code.
From the first post - the last line of what
On 9/12/07, Daniel Brown <[EMAIL PROTECTED]> wrote:
> On 9/12/07, Per Jessen <[EMAIL PROTECTED]> wrote:
> > Migrating from v4 to v5 is not necessarily straight forward.
> > Depending on what features you've used, you may have to rewrite some of
> > your code. For instance, we used the xslt sablotr
[snip]
Anyway, I think it's exceptionally poor show by php to cause a segfault,
probably due to user code. I know it does it every now and then, and
nobody has ever been interested in looking at the core dump.
[/snip]
The Dev team looks at core dumps all of the time to try to figure out
bugs and
On 9/12/07, Per Jessen <[EMAIL PROTECTED]> wrote:
> Migrating from v4 to v5 is not necessarily straight forward.
> Depending on what features you've used, you may have to rewrite some of
> your code. For instance, we used the xslt sablotron interface, which
> no longer exists in php5. Had to rewr
Stut wrote:
>> Hi Zbigniew
>>
>> Maybe it's worth doing some googling for wordpress and php5? If it's
>> not your code, it's not easy to debug. I have seen the apache core
>> dump many times, sometimes caused by obvious errors, other times by
>> something obscure and difficult to find.
>
> Com
Per Jessen wrote:
Zbigniew Szalbot wrote:
No, basically I just use wordpress on this site and that's all. No
fancy or advanced scripting, etc. It is family machine for family
issues. I can try and go back to v4 but I do think v5 should work just
as fine. At least I hope so.
Hi Zbigniew
Maybe
Zbigniew Szalbot wrote:
Hi there,
No, basically I just use wordpress on this site and that's all. No
fancy or advanced scripting, etc. It is family machine for family
issues. I can try and go back to v4 but I do think v5 should work just
as fine. At least I hope so.
Does phpinfo work? What doe
Zbigniew Szalbot wrote:
> No, basically I just use wordpress on this site and that's all. No
> fancy or advanced scripting, etc. It is family machine for family
> issues. I can try and go back to v4 but I do think v5 should work just
> as fine. At least I hope so.
Hi Zbigniew
Maybe it's worth do
Hi there,
2007/9/12, Per Jessen <[EMAIL PROTECTED]>:
> Zbigniew Szalbot wrote:
>
> > Hello,
> >
> > 2007/9/12, Edward Kay <[EMAIL PROTECTED]>:
> >>
> >> What do the Apache error logs say?
> >
> > Nothing that would be of help:
> >
> > httpd-error.log
> > [Wed Sep 12 09:04:17 2007] [notice] mod_sec
Zbigniew Szalbot wrote:
> Hello,
>
> 2007/9/12, Edward Kay <[EMAIL PROTECTED]>:
>>
>> What do the Apache error logs say?
>
> Nothing that would be of help:
>
> httpd-error.log
> [Wed Sep 12 09:04:17 2007] [notice] mod_security/1.9.4 configured
>
> A new such line is added when I try to start a
Hello,
2007/9/12, Edward Kay <[EMAIL PROTECTED]>:
>
> > Dear all,
> >
> > I hope you can help me. I am running FreeBSD 6.2 and I decided to
> > upgrade from php 4.4.7_1 to php5-5.2.3_1. However, after removing php4
> > and installing php5 and php5-extensions I am unable to start apache.
>
> What d
> Dear all,
>
> I hope you can help me. I am running FreeBSD 6.2 and I decided to
> upgrade from php 4.4.7_1 to php5-5.2.3_1. However, after removing php4
> and installing php5 and php5-extensions I am unable to start apache.
What do the Apache error logs say?
Edward
--
PHP General Mailing Li
63 matches
Mail list logo
