Re: Argh. Why is this happening to me?
Valdis.Kletnieks(a)vt.edu wrote:
Blame configure. ;) It found the Motif libs, so it used them...
That's reasonable. The help says:
--with-xim=xlib Compile with support for X input methods,
--with-xim=motif (*) Used in conjunction with Mule support.
Use either raw Xlib to provide XIM support, or
the Motif XmIm* routines (when available).
NOTE: On some systems bugs in X11's XIM support
will cause XEmacs to crash, so by default,
no XIM support is compiled in, unless running
on Solaris and the XmIm* routines are detected.
That clearly isn't true. I certainly didn't ask for XIM, but got it
anyhow. If anything, "xlib" should be the default.
> OpenMotif?
OpenMotif 2.1.30-6 RPMs on the RedHat box, Motif 2.1 on the AIX box that
gets hit by the problem as well.
Additional info:
./configure --with-widgets=no --with-dialogs=no --debug=no --error-checking=none
--with-mule=yes '--cflags=-Wall -Winline -Wmissing-prototypes -Wmissing-declara
tions -Wno-switch -Wpointer-arith -Wno-sign-compare -Wno-uninitialized -Wshadow
-g -pipe -s'
will survive at most 3 invocations of 'gnuclient /etc/motd' (and usually
crashes on trying to leave the first try). Using --with-mule=no produced
an xemacs that survived 14 invocations before I got bored. I've now cycled
through alternate builds with mule=no and mule=yes 3 times, and it seems to
only crash on Mule builds.
Note: this doesn't seem to be specific to gnuserv; for me, "C-x 5 2"
then "C-x 5 0" causes instant segfault, with the familiar backtrace.
Diagnosis: Motif and MULE don't get along. I'm not sure
what level of
show-stopper it is - I may be the only bozo trying to build with both
Mule and Motif.
Nope; although I only use one frame, so I never noticed it until I
actually went looking.
More additional info: --with=mule=yes --with-xim=xlib and Athena
widgets/dialogs works as well. Seems like the instant you allow Motif
to be linked in for *anything* (even XIM) it breaks Mule.
What about if you use Motif for everything *except* XIM?
I'm wondering if this has anything to do with the "VendorShell"
wierdness? This is one aspect of Xt I truly never got a handle on.
Both libXaw and libXm define vendorShellClassRec and
vendorShellWidgetClass. Past experience suggests that linking against
both can have odd consequences; the order in which the libraries are
specified in the link command can have an effect.
--
Glynn Clements <glynn(a)sensei.co.uk>