Martin v. Löwis added the comment: 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). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15898> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
