Follow-up Comment #2, bug #44240 (project gnustep):
That change looks reasonable to me and fixes the problem.
However, I think that there's also an issue with the -ignoreReadDescriptor and
-ignoreWriteDescriptor methods from NSFileHandle. It looks fairly stupid to me
to create a new run loop for the current thread when are just about to delete
the thread and its run loop. But what looks worse to me is that this code will
remove the file descriptor from the run loop of the current thread only. It
doesn't handle the case where the file descriptor is added to the run loop of
a secondary thread, but then closed on the main thread (or vice versa). My
feeling is that if we call -removeEvent:type:forMode:all: we should do that
for all (and only those) run loops that currently exist.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44240>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
