[issue16929] poll()/epoll() are not thread-safe

2013-01-11 Thread Charles-François Natali
New submission from Charles-François Natali: After optimizing epoll() to use a per-instance buffer like poll() does (http://bugs.python.org/issue16876), I realized that it wasn't thread-safe, and can result in crashes: ./python /tmp/test.py *** glibc detected *** ./python: free(): corrupted

[issue16929] poll()/epoll() are not thread-safe

2013-01-11 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: For poll() see issue8865. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16929 ___

[issue16929] poll()/epoll() are not thread-safe

2013-01-11 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +select.poll is not thread safe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16929 ___

[issue16929] poll()/epoll() are not thread-safe

2013-01-11 Thread Charles-François Natali
Charles-François Natali added the comment: OK, I'll close as duplicate. -- dependencies: -select.poll is not thread safe resolution: - duplicate superseder: - select.poll is not thread safe ___ Python tracker rep...@bugs.python.org

[issue16929] poll()/epoll() are not thread-safe

2013-01-11 Thread Charles-François Natali
Changes by Charles-François Natali cf.nat...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16929 ___ ___