Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!usc!trwind!venice!jeffery
From: jeffery@venice.SEDD.TRW.COM (Jeffery Cavallaro)
Newsgroups: comp.windows.x.motif
Subject: MORE DIALOG BOX PROBLEMS
Message-ID: <1020@venice.SEDD.TRW.COM>
Date: 1 Mar 91 03:24:58 GMT
Reply-To: jeffery@venice.sedd.trw.com (Jeffery Cavallaro)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 34

I have noticed that a lot of problems regarding dialog boxes and segmentation
faults have been appearing on this list.  A lot of the crashes that we get are
resource database sensitive.  Namely:

	Changing the binds can cause a crash.
	Modal settings always crash.
	Some crashes occur even BEFORE dialog boxes are even created!

Our application really beats on the toolkit and the widgets in strange ways,
so I think that we have exposed some underlying gotcha's in X11R4/MOTIF 1.1
that weren't there in X11R3/MOTIF 1.0.

The strangest point is that modal-related crashes occurred when a MODAL value
was set with the widget prior to manage time (XRDB, arglist, or XtSetValues).
Upon tracing back the stack, I found that the widget was accessing the XRDB
in the manage method!!!   IS THIS CORRECT!?!?!

Does this ring a bell with anyone?  It appears that MOTIF is screwing around
with the XRDB when it shouldn't.  Frankly, we are perplexed.  The next step is
a big debug session into the MOTIF libraries.

Any info before we embark on this would help.

By the way:

	HP9000s300
	HP-UX 7.0
	MIT X11R4 (patch level 18)
	OSF MOTIF 1.1

By the way, backing store doesn't even work on these platforms, so I thumb my
nose at AT&T.

Jeff