[Jim: I don't have the Debian bug number so I'm directing this to
you; my apologies, please forward. NB: I'm in the process of
releasing 21.4.10, it is available from CVS now via the release-21-4
tag, and will be on the ftp site in an hour or so, and official
announcement to follow.]
Michael, thanks for copying both lists; a crash is always an XEmacs
(upstream) bug, but I'm sure the Debian maintainer appreciates knowing
you're already in contact.
>>>> "Michael" == Michael Below
Michael> On doing this xemacs crashed.
I think this is fixed, please upgrade. I can't reproduce with 21.4.9
Debian is at 21.4.8; there was an important GCPRO bug fixed in
21.4.9, so you may not get relief until Debian releases something newer.
Michael> I was asked to look for a file called core,
Most Linux distros do the equivalent of "ulimit -c 0", which inhibits
production of core files. Do "ulimit -c unlimited".
I think the policy of inhibiting core dumps is brain-damaged; people
using stable apps won't see very many core dumps, but when they do
it's definitely worth the risk that the dumps will start to fill up
the disk. Is it really so hard to
echo "locate core" > /etc/cron.daily/find-cores
Michael> And a last one: the uname below is wrong, probably its
Michael> from the Debian package maintainer's system.
That's right; the Installation string is compiled into XEmacs at build
time. We're looking at ways to get the runtime uname information, but
we need to make it work on Windose and Mac too, if possible.
 GCPRO bugs almost always result in crashes that can only be
debugged because they go away when you fix the bug. :-/
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.