[issue19044] getaddrinfo raises near-useless exception
Balazs added the comment: Hi, this is the platform: Linux cloudbackupbr 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:52:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux /bin/bash: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=0x6db033ec6858b391e114e252b3354ddbf5a9f7be, stripped Thanks -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19044] getaddrinfo raises near-useless exception
Charles-François Natali added the comment: Well, as Ned explained, that's a libc bug. If getaddrinfo() fails with EAI_SYSTEM, errno should be set. There's nothing more Python can do. If the error is reproducible, you can run the failing code with strace, to see what's going on (and check if there's a more recent glib version which could fix this bug). -- resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19044] getaddrinfo raises near-useless exception
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19044] getaddrinfo raises near-useless exception
Changes by Balazs czv...@gmail.com: -- nosy: +balazs ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19044] getaddrinfo raises near-useless exception
New submission from Nikolaus Rath: I received a bugreport for a Python application that contains the following stacktrace: File /usr/lib/python3.3/http/client.py, line 1057, in endheaders self._send_output(message_body) File /usr/lib/python3.3/http/client.py, line 902, in _send_output self.send(msg) File /usr/lib/python3.3/http/client.py, line 840, in send self.connect() File /usr/lib/python3.3/http/client.py, line 1194, in connect self.timeout, self.source_address) File /usr/lib/python3.3/socket.py, line 417, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): OSError: [Errno 0] Error My guess is that something went wrong with the name resolution, but it seems near impossible to handle this in the application because apparently the exception contains no machine usable useful informaton at all. It would be nice if whatever information Python used to determine that the getaddrinfo call failed could be included in the exception, so that it can be properly caught and handled. -- components: Library (Lib) messages: 198039 nosy: Nikratio priority: normal severity: normal status: open title: getaddrinfo raises near-useless exception type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19044] getaddrinfo raises near-useless exception
Ned Deily added the comment: This looks like a platform bug. What platform was this running on? A web search turns up other reports of the system getaddrinfo() returning errno = 0 due to a glibc bug, for example, https://bugzilla.redhat.com/show_bug.cgi?id=958652. -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19044 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com