Re: build problem with-mule
"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes:
I received only one response to this build problem of mine. (Thank
you,
Ienaga-san!)
Sorry, about this. We have seen this crash a couple of times, but have
not yet figured out what is causing it.
If you only want a working xemacs then you can probably just supply
'--gung-ho' as an extra configure option.
I need any help on this. I have the following questions.
(1) All the statements of src/mule-coding.c are commented out by "#if 0"
I.e. src/mule-coding.c is null. Is this OK?
yes.
(2) I re-ran configure with --debug but "make" still
invokes cc with -xO4;
no -g is supplied. What is wrong ?
use --with-cflags=-g
(3) Is there a general guideline of how to debug coredump of temacs
or xemacs?
How do I stop temacs just before starting processing "update-elc.stamp",
so that temacs can be run in a single step mode from there?
see FAQ 2.1.16.
dbxrc defines a command 'update-elc' which you can use.
To debug gc problems you should:
- read the XEmacs Internals manual
- try setting always_gc=1 to get a crash early
- try using watchpoints, if some memory location is corrupted
accidentally.
I'm also still investigating this problem.
good luck.
Gunnar
--
Gunnar Evermann
Speech, Vision & Robotics Group
Engineering Department
Cambridge University