-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OverflowError: can't convert negative value to size_t #533
Comments
OS, Python version, Cython version, compiler, etc.? Can you provide a reproduction script? |
Still the same configuration as in #531 (Memory leak (and other problems) with send_string() and recv_string()) but now with current master and basically the same scripts: Server: import zmq
cx = zmq.Context()
so = cx.socket(zmq.ROUTER)
so.bind('tcp://127.0.0.1:3333')
while True:
p = so.recv()
m = so.recv_unicode() Client: import zmq
import time
cx = zmq.Context()
so = cx.socket(zmq.DEALER)
so.connect('tcp://127.0.0.1:3333')
s = '**********************************************************'
for i in xrange(100000):
so.send_unicode(s, copy=False)
time.sleep(.0001)
so.close()
cx.term()
raw_input('Finished. ') The client gets:
Unit testing comes to my mind ... |
Sorry, I don't see where you answered these before: What are your OS and Cython versions? Your scripts do not produce an error on any of my machines with current master ( (Debian Ubuntu, OS X). Can you make sure you do a clean checkout and install of pyzmq? It may be that you have a partial upgrade of pyzmq.
Do the existing tests pass for you ( |
uname -a is
Cython version is 0.20.1 I downloaded the current master package as a zip-file and installed it with pip. I had to upgrade Cython for that. The installation was successful. The nosetests for zmq displayed a lot of those |
What is |
2147483647 |
That's what I thought. I bet there is a bug that doesn't handle 32b properly. Now we are on the right track, at least. I'll make a 32b VM, and see if I can reproduce the error, then I can start figuring out what's wrong. Do you have access to a 64b machine? If so, can you confirm that you don't see the issue there? |
Unfortunately not. I can only help you with 32-bit testing. This will still be around for a while ;) |
I think I found it, can you test #534? |
If you confirm that #534 fixes this issue, I can probably cut a 14.2 release tomorrow. |
Yep, looks good now. |
Thanks! |
When using the new master, send(_string)? with copy=False yields
The text was updated successfully, but these errors were encountered: