Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: found possible suspect for characters out of order bug X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Tue, 11 Sep 2001 10:39:57 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: found possible suspect for characters out of order bug Thread-Index: AcE6WkhSvyTHhF/aTRKFzC3T8isX/w== From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA08010 Remember the bug that keeps getting odd reports? Well I've got it happening regularly to me at home. I couldn't discuss it last night - no internet connection :[. What I think is happening is that the fhander_termios edit_line method is getting called as a signal. If any out of order queueing occurs with signals, that would cause the percieved symptoms. It only happened during heavy system load - this is an emulated machine - which is to say any swapping or high CPU would cause it. It also only appeared to occur during type-ahead occurences. I'm still unable to debug, and I've never seen this happen to my win2k partition (which is gotten at via reboot :} ) so what I can do is limited. Questions for the group though: Are whatever windows signals are before they hit cygwin time-order guaranteed? Are cygwin signals time-order guaranteed? Are signal handlers expected to be reentrant? Rob