ID: 30770 Comment by: phil dot brennan at gmail dot com Reported By: chris at christopher-dean dot co dot uk Status: No Feedback Bug Type: Apache2 related Operating System: FreeBSD 5.2.1 PHP Version: 5.0.2 New Comment:
Hi, I get the exact same error as chris. I'm running the same release of freebsd, apache 2.0.53 and php 4.3.10. Apache2 on freebsd is built with the prefork mpm. Thats what I'm using. I realise that this may be a freebsd issue, but it is strange that this is the only part of php that is affected. I suppose its time for me to start digging through the source to php mail() now. Previous Comments: ------------------------------------------------------------------------ [2004-12-14 01:00:02] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2004-12-07 00:59:55] [EMAIL PROTECTED] Are you using the worker MPM? Threads on FreeBSD are historically a bit flaky. Google finds random similar backtraces from e.g. ruby users, FWIW. ------------------------------------------------------------------------ [2004-11-13 10:11:02] chris at christopher-dean dot co dot uk Results of the back trace: Couldn't get a core file so used method described on webpage for people who can't get a core file and this output was produced. Note, this is only the section of the backtrace where the crash occured from running the script in the browser, as prior to this it was all "no debugging symbols found" as apache starts normally: ----------------------------------------------------------- (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)... Program received signal SIGABRT, Aborted. 0x283bddcf in kill () from /lib/libc.so.5 (gdb) bt #0 0x283bddcf in kill () from /lib/libc.so.5 #1 0x283b2878 in raise () from /lib/libc.so.5 #2 0x2842af82 in abort () from /lib/libc.so.5 #3 0x2962a565 in _thread_exit () from /usr/lib/libc_r.so.5 #4 0x29628345 in _thread_kern_sig_undefer () from /usr/lib/libc_r.so.5 #5 0x29627a94 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #6 0x29627445 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 ----------------------------------------------------------- I hope this helps ------------------------------------------------------------------------ [2004-11-13 01:58:45] [EMAIL PROTECTED] 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. ------------------------------------------------------------------------ [2004-11-13 01:45:39] chris at christopher-dean dot co dot uk Forgot to mention, the email does get sent ------------------------------------------------------------------------ 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/30770 -- Edit this bug report at http://bugs.php.net/?id=30770&edit=1
