Message 79429 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	jyasskin
Recipients	collinwinter, jyasskin
Date	2009年01月08日.19:08:12
SpamBayes Score	0.013315474
Marked as misclassified	No
Message-id	<1231441695.4.0.529827841073.issue4884@psf.upfronthosting.co.za>

Content
glibc until 2.10 has a bug in gethostbyaddr_r that assumes the buffer argument is 8-byte aligned (http://sources.redhat.com/ml/libc-alpha/2009-01/msg00000.html). gcc seems to always provide such alignment for the call in socketmodule.c:socket_gethostbyaddr(), but llvm-gcc (possibly only HEAD, not 2.4) does not, which causes a segfault in test_socket.py. The llvm bug investigating the problem is http://llvm.org/bugs/show_bug.cgi?id=3233. The attached patch specifies the alignment so that llvm-gcc and unfixed glibcs work together. I'll commit this tomorrow if there are no objections.

Content

glibc until 2.10 has a bug in gethostbyaddr_r that assumes the buffer
argument is 8-byte aligned
(http://sources.redhat.com/ml/libc-alpha/2009-01/msg00000.html). gcc
seems to always provide such alignment for the call in
socketmodule.c:socket_gethostbyaddr(), but llvm-gcc (possibly only HEAD,
not 2.4) does not, which causes a segfault in test_socket.py. The llvm
bug investigating the problem is http://llvm.org/bugs/show_bug.cgi?id=3233.
The attached patch specifies the alignment so that llvm-gcc and unfixed
glibcs work together.
I'll commit this tomorrow if there are no objections.

History
Date	User	Action	Args
2009年01月08日 19:08:15	jyasskin	set	recipients: + jyasskin, collinwinter
2009年01月08日 19:08:15	jyasskin	set	messageid: <1231441695.4.0.529827841073.issue4884@psf.upfronthosting.co.za>
2009年01月08日 19:08:14	jyasskin	link	issue4884 messages
2009年01月08日 19:08:13	jyasskin	create

homepage