|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #72256 echo statement on invalid fd cause php to abort
Submitted: 2016-05-23 07:32 UTC Modified: 2021-12-15 14:01 UTC
Avg. Score:2.3 ± 0.9
Reproduced:1 of 2 (50.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: prinbra at gmail dot com Assigned: cmb (profile)
Status: Assigned Package: *General Issues
PHP Version: Irrelevant OS:
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.
Block user comment
Status: Assign to:
Bug Type:
From: prinbra at gmail dot com
New email:
PHP Version: OS:


 [2016-05-23 07:32 UTC] prinbra at gmail dot com
on cli environment, when the stdout of php becomes unavailable, eg: user run php in background and logged out of their ssh connection.
a echo statement will cause php process to exit immediately!

strace output:

14937 12:22:18.958295 write(1, "running\n", 8) = -1 EIO (Input/output error)

then php just silently quit!


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2016-05-25 20:46 UTC]
Thanks for the report. When user is logged out, the whole session becomes invalid. This should be solvable by using nohup or running PHP in screen/tmux.

 [2016-05-27 05:13 UTC] prinbra at gmail dot com
er, my point is: may be the php process shouldn't quit if echo failed.

the fail of fprintf  does not cause php to quit? why echo is so special and so fragile?

fprintf(STDOUT, "hello, world\n");
fprintf(STDOUT, "hello, world2\n");
fprintf(STDERR, "hello, world2 in stderr\n");

hello, world
PHP Warning:  fprintf(): 2 is not a valid stream resource in /tmp/t.php on line 4
hello, world2 in stder

however, if change fprintf to echo, php will quit early.
 [2021-12-15 14:01 UTC]
-Assigned To: +Assigned To: cmb
 [2021-12-15 14:01 UTC]
Behavior confirmed: <>.

Interestingly, running the script on a debug version of PHP,
won't exhibit this behavior.  Instead, I get:

    hello, world
    hello, world2
    hello, world2 in stderr

> the fail of fprintf  does not cause php to quit? why echo is so
> special and so fragile?

To begin with, fprintf() explicitly requests the resource, and
notices that it has been closed, so it doesn't actually try to
write anything to stdout (the warning goes to stderr by default).
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Apr 23 21:01:31 2024 UTC