#36626 [Sus->WFx]: Crash (seems in uksort)

ID: 36626 Updated by: jani@php.net Reported By: fcartegnie at nordnet dot fr -Status: Suspended +Status: Wont fix Bug Type: Reproducible crash Operating System: Linux PHP Version: 4.4.2 New Comment: We are sorry, but we can not support PHP 4 related problems anymore. Momentum is gathering for PHP 6, and we think supporting PHP 4 will lead to a waste of resources which we want to put into getting PHP 6 ready. Previous Comments: ------------------------------------------------------------------------ [2006-03-06 16:40:10] derick@php.net Then we can't help. Please reopen if you can provide a reproducing script. We will not debug a whole application, and definitely not under an NDA. ------------------------------------------------------------------------ [2006-03-06 14:56:58] fcartegnie at nordnet dot fr Again, it's impossible to isolate a reproduce code, as it loads and initialize a really complex system. Code does not reproduce crash on my other computer (2.6.15). So it may not work elsewhere :( The only thing I can do, it to give ssh access to browse code & run debugger. All with non-disclosure agreement. ------------------------------------------------------------------------ [2006-03-06 14:44:09] tony2001@php.net We still need a reproduce code. ------------------------------------------------------------------------ [2006-03-06 13:58:33] fcartegnie at nordnet dot fr Well, as far as I've gone, I've fixed my php code. I use a global class which handles mysql connections.(no reconnects each time, but without persistent connexion) The sigsev comes when I use the existing sql connection from inside the uksort user_functions. Creating a new class from there make it works :( ------------------------------------------------------------------------ [2006-03-06 13:39:06] fcartegnie at nordnet dot fr no can't do sir :( I can't isolate a subset of calls wich creates crash. I'm only able to produce it with full data & code. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/36626 -- Edit this bug report at http://bugs.php.net/?id=36626&edit=1