"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
I infer that you are able to reproduce the crash. Good. This time,
start XEmacs with the commands
bash$ gdb `which xemacs` # note backquotes
(gdb) run essay11.tex
Then when XEmacs crashes,
(gdb) where
and collect the output and send it to us.
Alternatively start by doing `ulimit -c unlimited' in the xterm, then
start xemacs in exactly the same way. When xemacs crashes, there
should be a core file in the current directory, named core. Do `gdb
`which xemacs` core', then type `where' at the gdb prompt and collect
the output and send it to us. However, running under gdb is preferred
because gdb is likely to preserve the stack better.
Stephen's advice for getting a backtrace is good, and will help us
debug the problem. As a shot in the dark, are you sure you're using
the Athena3d widgets? This might be one of those Athena3d vs. Athena
problems? What happens if you configure and build
'--with-dialogs=athena'?
If that fails, please try to generate a backtrace.
- vin