|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2009-09-18 19:01 UTC] jani@php.net
[2009-09-26 01:00 UTC] php-bugs at lists dot php dot net
[2009-12-05 15:16 UTC] sfsys at mail dot ru
[2009-12-15 00:40 UTC] felipe@php.net
[2009-12-22 01:00 UTC] php-bugs at lists dot php dot net
|
|||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Thu Oct 30 07:00:02 2025 UTC |
Description: ------------ I've noticed that some errors in stream_socket_client()s connection don't populate errstr with an error. As far as I can tell, errno is always populated. The most consistent case I've found for this if when the error code is 16 - $errstr SHOULD be "Device or resource busy" (according to some googling), however, it is empty. I've also come across many errono's that are > 127 and have no errstr. e.g. 5736689 Reproduce code: --------------- Unless someone knows how to reproduce "Device or resource busy", then I can't create any code to reproduce errno 16 having no errstr. I can reproduce the oddly high errno's (with no errstr) as the example above appears to be for invalid URLs: <?php $stream = stream_socket_client('tcp://tinyu:80', $errno, $errstr); echo "$errno\n"; echo "'$errstr'\n"; Expected result: ---------------- Not sure what the error number *should* be, possibly 22 (EINVAL), Invalid argument. I'll go with that: 22 'Invalid argument' Actual result: -------------- 5736689 ''