php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #37758 SIGINT signals screw with further posix_kill() calls
Submitted: 2006-06-09 08:06 UTC Modified: 2006-08-07 01:00 UTC
From: aeolianmeson at blitzeclipse dot com Assigned:
Status: No Feedback Package: Semaphore related
PHP Version: 5.1.4 OS: Fed4
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: aeolianmeson at blitzeclipse dot com
New email:
PHP Version: OS:

 

 [2006-06-09 08:06 UTC] aeolianmeson at blitzeclipse dot com
Description:
------------
When a SIGINT is sent via CTRL+C or CTRL+BREAK, the handler is called. If this handler sends a SIGTERM to other children, the signals are not received.

SIGINT can be sent via posix_kill() and it work exactly as expected-- This only applies when initiated via a hard break.

SIGTERM will also work perfectly.

Reproduce code:
---------------
http://www.blitzeclipse.com:81/breakhandle.php

Expected result:
----------------
Once the main process, its child, and that child's child are up, pressing CTRL+C or CTRL+BREAK should cause the first process to terminate the second process, and the second process should then terminate the third process.

Actual result:
--------------
When CTRL+C or CTRL+BREAK is pressed, the first process terminates, and nothing else responds.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-06-10 20:28 UTC] aeolianmeson at blitzeclipse dot com
Also, I've noticed that even when SIGINT is handled, it will close down children. I could draw up a program if this appears to be unrelated.
 [2006-06-19 02:36 UTC] aeolianmeson at blitzeclipse dot com
I was wondering if there was some change in the status of this issue.

Dustin
 [2006-07-30 22:07 UTC] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.


 [2006-08-07 01:00 UTC] 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".
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat Nov 27 03:03:12 2021 UTC