Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!hellgate.utah.edu!cranial.utah.edu!ddebry
From: ddebry%cranial.utah.edu@cs.utah.edu (David DeBry)
Newsgroups: comp.windows.x
Subject: XInput extension test programs
Summary: Are they really supposed to work?
Message-ID: <1990Feb22.145615.10380@hellgate.utah.edu>
Date: 22 Feb 90 21:56:15 GMT
Sender: David DeBry  (ddebry@ug.utah.edu)
Distribution: usa
Organization: University of Utah CS Dept
Lines: 25

.
	I've been trying to build the xinput extension test programs that
came with the r4 release.  I'm on a mips based unix box.  Maybe I'm missing
the point entirely here, but when you use anything from the X toolkit, 
doesn't that disallow any normal IO unless it's done through X?  Because
when I try to run the newly built tests, I get segmentation faults.  The
faults are occurring at simple statements like printf, fprintf, etc.

	If the programs are using the toolkit, why are they expected to work
when normal IO is being attempted outside of X?

	A mail reply would be appreciated (as well as posting), because I
don't get a lot of chances to read the area, and consequently get backlogged.

///  David DeBry /// UM24 : Theta=285 R=100 Phi=087 /// (801) 272 - 3094  ///
///      "It is pitch black.  You are likely to be eaten by a Grue."      ///
/// I-NET: ddebry@ug.utah.edu /// UUCP: uunet!iconsys!caeco!i-core!ddebry ///
///  Snail Mail : 4223 Camille Drive   Salt Lake City, Utah   84124-2802  ///



///  David DeBry /// UM24 : Theta=285 R=100 Phi=087 /// (801) 272 - 3094  ///
///      "It is pitch black.  You are likely to be eaten by a Grue."      ///
/// I-NET: ddebry@ug.utah.edu /// UUCP: uunet!iconsys!caeco!i-core!ddebry ///
///  Snail Mail : 4223 Camille Drive   Salt Lake City, Utah   84124-2802  ///