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.

Author loewis
Recipients amoffat, loewis, ned.deily
Date 2012-09-12.08:41:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <50504AD6.2010209@v.loewis.de>
In-reply-to <1347347489.99.0.712013874119.issue15898@psf.upfronthosting.co.za>
Content
Am 11.09.2012 09:11, schrieb Andrew Moffat:
> I'm not sure I follow the problem exactly.  So you're saying that the
> failing version uses _cancel sys calls, and that __pthread_testcancel
> may result in EINTR.  But that this is not happening in the trace,
> and data is being written successfully.  I guess I'm wondering where
> the written bytes went and if there's any way to retrieve them?

That's exactly the question, and why I say that is must be an OS bug.
According to the trace, the OS accepted the data, so if they got lost,
it's their "fault".

Unfortunately, the dtruss doesn't decode the ioctl arguments, so it's
not easy to tell whether they are right. You could try running it with
-a to see whether this gives more information. Please don't paste
the traces, though, but attach them (the editing is surely appreciated,
though).
History
Date User Action Args
2012-09-12 08:42:21loewissetrecipients: + loewis, ned.deily, amoffat
2012-09-12 08:41:59loewislinkissue15898 messages
2012-09-12 08:41:59loewiscreate