From 2bc136e680877b6a9d17d6a0e815b47775088d67 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 9 May 2011 10:47:56 +0200 Subject: IRC. --- open_issues/select_bogus_fd.mdwn | 55 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 open_issues/select_bogus_fd.mdwn (limited to 'open_issues/select_bogus_fd.mdwn') diff --git a/open_issues/select_bogus_fd.mdwn b/open_issues/select_bogus_fd.mdwn new file mode 100644 index 00000000..17aced4a --- /dev/null +++ b/open_issues/select_bogus_fd.mdwn @@ -0,0 +1,55 @@ +[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_glibc]] + + +# Python + +IRC, freenode, #hurd, 2011-04-13 + + ok, cause of first python testsuite failure located, now the + hard part, how to best fix it :) + how to redesign the code to avoid the problem... that's the + hard part, mostly cause i lack contextual info + tschwinge: the problem is pretty much summarized by this + comment in _hurd_select (in glibc): /* If one descriptor is bogus, we + fail completely. */ + does POSIX say anything about what to do if one fd is invalid? + and the other question is why python is calling select() with an + invalid fd + pochu: yep, it says it should not fail completelly + then that's our bug :) + abeaumont: just note that (at least on debian) some tests may + hang forever or cause hurd/mach to die + abeaumont: see in the debian/rules of the packaging of each + pythonX.Y source + ... there's a list of the tests excluded from the test suite run + well, to be precise, python has a configure check for + 'broken_poll' which hurd fails, and therefore python's select module is + not built, and anything depending on it fails + broken_poll checks exactly for that posix requirement + the reason for python using a non-existant + descriptor... unknown :D + we should fix select to not fail miserably in that case + abeaumont: we have a patch to fix the broken poll check to + actually disable the poll module + pinotree: but the proper fix is to fix select(), which is what + abeaumont is looking at + pinotree: i'd say that's exactly what python's configure check + does itself -- disable building the select module + abeaumont: what pinotree means is that the check is broken, see + http://patch-tracker.debian.org/patch/series/view/python2.6/2.6.6-8/hurd-broken-poll.diff + yes, the configure check for poll does the check, but not + everything of the poll module gets disabled (and you get a build failure) + +--- + +See also [[select]] and [[select_vs_signals]]. -- cgit v1.2.3