Faried> I just rebuilt it to use athena (Xaw3d, in my case) Faried> dialogs and widgets and it doesn't crash any more. Motif. Buggy Dialogs since 1993. Although maybe this isn't Motif's fault.... Faried> If it helps, the crashy xemacs was linking against Faried> open-motif 2.2.2. I don't think it really does. libXm doesn't appear in your C backtrace. If Motif is really related, this is either a Heisenbug (any change in the link would make it go away) or somewhere XEmacs and libXm are not handshaking properly, so XEmacs has a different idea of the window configuration from libXm. Of course, it could just be Motif's historic bugginess. Damn that X11 policy of "our refusal to sanity check arguments is your problem" anyway! Since we recently replaced C window config routines with a few C lowlevel functions and Lisp, my bet is that we missed an #ifdef HAVE_MOTIF somewhere. Mike, any thoughts? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

Truth of the matter is, I skimmed the output of ./configure --help and missed the part that said using lucid dialogs really meant using motif. I never meant to use motif, and this never bit me in the past because I never had motif installed on my system. Since contemporary hardware makes recompiling XEmacs take no more than five minutes (if that), and since the test case that causes the crash is trivial to reproduce, I'm willing to investigate this problem further, or test fixes, or whatever. Faried.