#25053 [Fbk->Opn]: seg fault

ID: 25053 User updated by: kevin at oceania dot net Reported By: kevin at oceania dot net -Status: Feedback +Status: Open Bug Type: InterBase related Operating System: linux PHP Version: 4CVS-2003-08-12 (stable) Assigned To: abies New Comment: installed php4-STABLE-200308170330 segfault still persists Previous Comments: ------------------------------------------------------------------------ [2003-08-16 18:27:57] abies@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip I suspect the reason for the segfault is the same as for bug #7014 (among others). The segfault will prevent you from seeing what the actual error is. This has been corrected in more recent CVS versions of PHP4 ------------------------------------------------------------------------ [2003-08-13 07:05:01] abies@php.net We really need a back trace, because I cannot reproduce the error by running the code you sent. ------------------------------------------------------------------------ [2003-08-12 22:18:24] kevin at oceania dot net url for single file that causes seg fault http://203.109.184.88/phoenix/segfault.phps ------------------------------------------------------------------------ [2003-08-12 09:20:27] sniper@php.net And provide a short but complete example script as those urls you provided do not work. Plus we won't bother with so many files anyway, you can easily provide ONE file which has all the necessary data. ------------------------------------------------------------------------ [2003-08-12 07:55:31] derick@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ 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/25053 -- Edit this bug report at http://bugs.php.net/?id=25053&edit=1