ID: 21040
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: Open
Bug Type: Apache2 related
Operating System: Solaris x86 2.7
PHP Version: 4.4.0-dev
New Comment:
No module/extension besides the ones shown in the configure command
line above (rewrite, expires, status, info). The configuration of the
FreeBSD test box is a copy of this one, and it works. Could it be that
the threads library itself is either taking over SIGPROF of blocking it
somehow?
I'm considering building Apache with an alternate threads library to
see what happens.
Previous Comments:
------------------------------------------------------------------------
[2002-12-16 10:51:57] [EMAIL PROTECTED]
Sounds like some is taking over the handler for the SIGPROF and it
never gets to PHP. Besides PHP, what modules/extensions do you have
enabled in your Apache?
------------------------------------------------------------------------
[2002-12-16 06:44:11] [EMAIL PROTECTED]
Works on FreeBSD 4.x (with unmodified PHP source).
So it's kind of Solaris-specific (will test on Sparc)
------------------------------------------------------------------------
[2002-12-16 05:12:57] [EMAIL PROTECTED]
[oops, posted this as "add comment" because I hadn't read the direction
to use "edit submission" instead yet --sorry]
Just out of curiosity, and admittedly not quite understanding what I
was doing, I have tried changing the zend_set_timeout code to use
SIGALRM instead of SIGPROF and thus pass ITIMER_REAL to setitimer
instead of ITIMER_PROF
Guess what? It works now.
I understand that this can have nasty side effects. I was just
wondering why SIGPROF was being used and if this could be the reason.
The setitimer man page on Solaris says a lot of things about using it
in MT environment which I don't quite catch :-)
------------------------------------------------------------------------
[2002-12-16 05:09:03] [EMAIL PROTECTED]
Just out of curiosity, and admittedly not quite understanding what I
was doing, I have tried changing the zend_set_timeout code to use
SIGALRM instead of SIGPROF and thus pass ITIMER_REAL to setitimer
instead of ITIMER_PROF
Guess what? It works now.
I understand that this can have nasty side effects. I was just
wondering why SIGPROF was being used and if this could be the reason.
The setitimer man page on Solaris says a lot of things about using it
in MT environment which I don't quite catch :-)
------------------------------------------------------------------------
[2002-12-16 05:08:07] [EMAIL PROTECTED]
reopened..(please don't add comments to your own bug report, use the
'Edit Submission' and change the status to open when you give
feedback.)
------------------------------------------------------------------------
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/21040
--
Edit this bug report at http://bugs.php.net/?id=21040&edit=1
