PHP 4.0 Bug #9082 Updated: getpeername() causes seg fault
| From: | mathieu@php.net | Date: | Sat, 03 Feb 2001 07:17:58 +0000 |
| Subject: | PHP 4.0 Bug #9082 Updated: getpeername() causes seg fault | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-45661@lists.php.net to get a copy of this message | ||
ID: 9082
Updated by: mathieu
Reported By: colin@php.net
Old-Status: Closed
Status: Feedback
Bug Type: Sockets related
Assigned To:
Comments:
[Status change]
and:
heh dunno wether it still does what it oughta now though :PPPP
can't test in your environment
Previous Comments:
---------------------------------------------------------------------------
[2001-02-02 15:57:06] cmv@php.net
Fixed in CVS ... thanks mathieu.
---------------------------------------------------------------------------
[2001-02-02 15:26:38] mathieu@php.net
[Status change]
and:
heh dunno wether it still does what it oughta now though :PPPP
can't test in your environment
---------------------------------------------------------------------------
[2001-02-02 14:46:52] mathieu@php.net
[Status change]
and:
heh dunno wether it still does what it oughta now though :PPPP
can't test in your environment
---------------------------------------------------------------------------
[2001-02-02 14:45:19] mathieu@php.net
Colin
For now I'm not in the CVS thingy to write to the PHP tree, but:
What fixed it for me is putting:
if (ZEND_NUM_ARGS() == 2)
MAKE_STD_ZVAL(*port);
after the ifstatement containing the zend_get_parameters().
-- CaPS
---------------------------------------------------------------------------
[2001-02-02 14:07:55] colin@php.net
The proto says:
getpeername(int fd, string &addr[, int &port])
But if I only pass it the $addr, my script segfaults.
i.e., this works:
<? getpeername($socket, &$ip, &$port); ?>
and this doesn't:
<? getpeername($socket, &$ip ); ?>
- Colin
---------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view the rest of the comments,
please view the bug report online.
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9082&edit=2