|
From: | Richard Frith-Macdonald |
Subject: | [bug #36684] GSSocketStream scheduleInRunLoop:forMode: does not |
Date: | Sun, 08 Jul 2012 14:51:28 +0000 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/534.57.2 (KHTML, like Gecko) Version/5.1.7 Safari/534.57.2 |
Update of bug #36684 (project gnustep): Status: None => Works For Me Open/Closed: Open => Declined _______________________________________________________ Follow-up Comment #1: I can't reproduce this and the sequence of operations described is precisely the normal usage used in the NSStream regression tests ... so it's done evey time anyone runs the testsuite (in Tests/base/NSStream/socket.m for instance). Perhaps if the reporter can provide source code for a minimal example/test to reproduce the problem (and details of the system the problem happened on), we can investigate ... but at the moment my best guess woud be that the problem might actually have been something like failing to run the runloop rather than a bug in base. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?36684> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |