Inconsistent (unsigned long) and (long) handling.
How
static bool
readResponse(rpcClient *cp, PyObject **bodyp, ulong blen)
and
...
if (blen < 0) {
later were supposed to work?
Moreover, the number of bytes was parsed as (int)
from the tuple, not as (long), which produced
"Connection timed out" on 64-bit platforms
(I have tried Solaris 8 and HP/UX 11.00).
rpcClient.c unsigned long patch
Logged In: YES
user_id=184164
I've applied the patch to the CVS archives. It will be
available in the next release. I've tried to fix a couple
more instances of things like this in rpcServer, but I
wouldn't be suprised if there are more in there.