Description of Problem:
Dumps core on start up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fatal error (11).
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x243e>)
# bind (debugger debug-on-error command-line-args-left)
# (unwind-protect ...)
# (condition-case ... . error)
# (catch top-level ...)
zsh: segmentation fault xemacs-21.4.5
No core dump.
Rebuilding without lesstiff-devel installed fixed the problem for me.
Rebuilding on your system should solve it even without that change - something
isn't quite right in that buildroot. Keeping open, will close when it's rebuilt
some day in the future.
Sounds like http://list-archive.xemacs.org/xemacs-beta/200110/msg00286.html ...
(solution is given there also)
He didn't use lesstif, so that theory is abandoned.
Bug in msg00286 is not a lesstif issue, but a binutils one (perhaps triggered by
I see similar coredumps with rawhide binutils-126.96.36.199.7-2, but
binutils-188.8.131.52.8-9 are working fine (I have not tried the solution from the
XEmacs maillist yet).
Hmmm, I see binutils-184.108.40.206.7-2 is in the buildroot...
Looks like this bug should probably be moved to binutils then.
Forget to add that indeed rebuilding 21.4.5-1 on a 7.2 box made the problem go
away as you said (ie binutils-220.127.116.11.8-9).
On second thoughts, after reading the whole thread on the xemacs-list it seems
this is due to an official change in binutils. So I agree with Enrico that we
should add those ld options to %configure.
On i386 at least I can reproduce the problem:
xemacs-21.4.5-1 built with binutils-18.104.22.168.7-2
dumps core for me at startup, whereas if I build with
binutils-22.214.171.124.8-9 it works fine.
Adding '--ldflags=-s -znocombreloc' to the configure options, fixes the problem
with binutils-126.96.36.199.7-2 as expected.
Strange, though. For xemacs-21.4.5-1, xemacs -nw runs ok in a tty -- it only
seems to dump core when starting in an X window.
fixed in xemacs-21.4.5-2.