Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU (Jim Fulton)
Newsgroups: comp.windows.x
Subject: re: Xlib question
Message-ID: <8908031516.AA04546@expo.lcs.mit.edu>
Date: 3 Aug 89 15:16:20 GMT
References: <8908021904.AA24408@scf1.fac.ford.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 18


You forgot to include several bits of information:

	o  what sort of platform you are using
	o  which C compiler you are using
	o  whose Xlib (and which release) you are using
	o  whether or not some of the variables were declared "register"
	o  what values the arguments to XSetStandardProperties had
	o  what the traceback from the core dump looked like
	o  a small, compilable example program that demonstrates the problem


I suspect that your program is walking on memory somewhere and that the problem
isn't in Xlib.  But, if can send me a small program, I'll try it here. 


Jim Fulton
MIT X Consortium