On Tue, 7 Sep 2004, Jim Grill wrote: > If any of the output from gdb give you a hint what the problem could be (ftp > functions or something) research each of the functions you are using on the > PHP site reading the user added comments. Look for any mention of a possible > segfault. Search the PHP bugs on http://bugs.php.net for your PHP version > using the name of the function and/or the name of the commands in the > backtrace. Chances are someone has already found the bug and there may be a > workaround or the problem has been fixed in CVS or in a newer version (in > your case PHP 4.3.9RC2). > > If you can't find anything relating to your problem on PHP.net, > bugs.php.net, or google then you should follow the proceedure for reporting > bugs on http://bugs.php.net/ . It's a thankless job, but it helps everyone > out in the long run if done properly. It will be much appreciated if you > follow the above steps and include sample code and gdb information when > submitting a bug. Leave it to the real pros to read the backtrace output!
Just to back this up, if you submit a bug report with a good backtrace (one from a non-stripped PHP, you don't necessarily need to recompile using enable-debug) the bug is 90% fixed. Reproducable segfaults on Unix are actually quite trivial to fix. Getting the clean backtrace is usually more work than fixing the actual bug. Thanks for the good explanation there Jim. -Rasmus -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
