[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Irit Katriel added the comment: Please create a new issue if you're still seeing this on 3.9+. -- nosy: +iritkatriel ___ Python tracker ___

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Charles-François Natali added the comment: I don't see anything wrong with the code. Could you try running the test under valgrind. You must build Python with --with-valgrind, and then: valgrind --tool=memcheck --suppressions=Misc/valgrind-python.supp test --

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Jeffrey Walton added the comment: This might be relevant. It showed up while building Python 3.3.5 from sources. /usr/local/bin/clang -fsanitize=undefined -fPIC -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude -I/usr/local/include

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

New submission from Jeffrey Walton: From Python head in mercurial: $ hg id 7ce22d0899e4+ tip Exporting set allocator_may_return_null=1 for Clang might tickle this issue. Without the export, this test did not fail. =

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Jeffrey Walton added the comment: This does not look quite right from Modules/sockewtmodule.c. /* Fill in an iovec for each item, and save the Py_buffer structs to release afterwards. */ if (nitems 0 ((iovs = PyMem_New(struct iovec, nitems)) == NULL ||

[issue20937] test_socket: buffer overflow in sock_recvmsg_guts

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +giampaolo.rodola, neologix, pitrou versions: +Python 3.3, Python 3.4 -Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20937 ___