I started a discussion here: http://www.mwusers.com/forums/showthread.php?t=9265 about some minor issues we are having over on the OpenOffice.org Wiki. A few pages here and there are causing a SegFault when the page is loaded. It was suggested I come to this mailing list to see if this can be sorted out.
The most likely cause has been traced back to double-byte characters in Categories, and is duplicable.
Example of a broken Wiki page: http://wiki.services.openoffice.org/wiki/OpenOffice.org%E6%97%A5%E6%9C%AC%E8... まとめ
A working page: http://wiki.services.openoffice.org/wiki/OOo_2.2.1%E3%81%AE%E6%97%A5%E6%9C%A...
Specifically, if you create a test page on the wiki and assign this Category syntax to it [[Category:品質管理]] it will cause the SegFault and the page will not be shown.
Is this known behavior? A bug? Something triggered by some odd configuration we have? (we are using a fairly basic setup with a limited number of extensions which are fairly well tested before installing)
Wiki config is here: http://wiki.services.openoffice.org/wiki/Special:Version
C.
Clayton wrote:
Wiki config is here: http://wiki.services.openoffice.org/wiki/Special:Version
Your PHP version is more than two years old. A *lot* of segfaulting bugs were fixed since then.
http://www.php.net/ChangeLog-5.php
Juliano F. Ravasi wrote:
Clayton wrote:
Wiki config is here: http://wiki.services.openoffice.org/wiki/Special:Version
Your PHP version is more than two years old. A *lot* of segfaulting bugs were fixed since then.
We are working on updating that soon. We're somewhat limited by the version of Coolstack/Solaris that is running on the Wiki server. There is an update to the Coolstack scheduled for early January which includes.. I hope.. a fresh version of PHP.
C.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Clayton wrote:
Juliano F. Ravasi wrote:
Clayton wrote:
Wiki config is here: http://wiki.services.openoffice.org/wiki/Special:Version
Your PHP version is more than two years old. A *lot* of segfaulting bugs were fixed since then.
We are working on updating that soon. We're somewhat limited by the version of Coolstack/Solaris that is running on the Wiki server. There is an update to the Coolstack scheduled for early January which includes.. I hope.. a fresh version of PHP.
The only "pure PHP" code that should ever cause a segfault is infinite recursion -- this eventually breaks the stack, causing a segfault. You can detect this condition more easily by installing the XDebug extension for PHP; this provides better error reporting for some problems, and will error out and give you a PHP-level stack trace at a give recursion threshold, making it easier to track down such problems.
If it's not that, then the most likely culprits are bugs in PHP or in an extension to PHP (including, perhaps, the PCRE regular expression library). Given a very old version of PHP, you're more likely to hit such a bug.
All I can really recommend for that other than just upgrading is hopping in with a hardcore debugger (eg gdb) to track down what part of PHP is crashing and get a C-level backtrace.
- -- brion
mediawiki-l@lists.wikimedia.org