Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!bu.edu!bu-cs!lectroid!cloud9!jjmhome!m2c!umvlsi!dime!dime.cs.umass.edu!moss From: moss@takahe.cs.umass.edu (Eliot &) Newsgroups: comp.lang.smalltalk Subject: Re: Bad-event-type notifier appearing sometimes Message-ID: Date: 3 Jan 90 14:42:49 GMT References: <1023@prlhp1.prl.philips.co.uk> Sender: news@dime.cs.umass.edu Reply-To: Moss@cs.umass.edu Organization: Dept of Comp and Info Sci, Univ of Mass (Amherst) Lines: 19 In-reply-to: gupta@prlhp1.prl.philips.co.uk's message of 19 Dec 89 11:23:02 GMT You did not indicate which implementation of Smalltalk you were running! Still, I can tell you this much. Smalltalk handles all input by having asynchronous interrupts put a note of what happened (mouse movement, button change, keyboard key down/up) in an internal queue and then noticing those *events* slightly later. Thus, as far as the operating system is concerned, Smalltalk is interrupt driven, but its internal structure is more like polling. Anyway, the notifier is saying it's finding a event in this internal structure that it does not understand. This sounds like a clear cut virtual machine bug to me. The fact that it happens at the beginning suggests an initialization problem or initial race condition. I'd say to get with your virtual machine supplier on it. Good luck! Eliot -- J. Eliot B. Moss, Assistant Professor Department of Computer and Information Science Lederle Graduate Research Center University of Massachusetts Amherst, MA 01003 (413) 545-4206; Moss@cs.umass.edu