bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.


From: Hin-Tak Leung
Subject: Re: emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.2)
Date: Mon, 12 May 2003 17:12:14 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

This is going more and more off-topic. My initial post was fairly
specific, and the one reply I got (asking why I don't use a more
current version) was already somewhat off-topic, because I did
describe my system in much detail and it would have been obvious even
at that point I had a (not yet disclosed) reason not to use a
more current version.

But unless of course, you would rather me switching to xemacs-21 instead...

(cemacs still continue to work under it, as the emacs/xemacs split
occurred before version 19, and the xemacs folks are less agressive
in making incompatible changes - which unfortunately is also the
reason of xemacs's bloatedness; however I believe MULE is going into
xemacs-24 or thereabout's so the issue will need to be addressed one day,
even if I switch to xemacs).

FWIW, I did search through the archive for "Fatal Error(11)".
And it seems to be the message for a general memory access error,
similar to the gcc's SIG 11 (probably identical to...), or
the rather uninformative "segmentation fault" whenever any program dies;
and fatal error 11 can occur under a lot of totally unrelated conditions,
but mostly to do with how undump works, memory aligment, etc.

So my guess is that it is probably going to be very sensitive
to how my glibc, Xfree86, or my gcc were configured and built and
any patches were applied to them; and there *might* be a chance
that a future system upgrade *might* magically fixes it.

In any case, the reality is that I only need emacs-19 to work in
the "-nw" enviroment for cemacs, and figuring out why it
segfaults under Xfree86 is a somewhat academic issue... but
I would still like an answer, an explanation, or (gasp) a
possible fix.

OTOH, if I really want a "currently supported" emacs for my purpose,
I could switch to xemacs-21 immediately and that would give me
a couple of years to look for other alternatives...

Thien-Thi Nguyen wrote:
Hin-Tak Leung <address@hidden> writes:

   Now back to my question: why emacs 19.34 segfault when built against
   glibc-2.3 and Xfree 4.3.0? And please stick to the question... - and
   please do not ask why I don't switch to xemacs, or use MULE.

in this case probably no one can answer your question w/o your investing
effort into debugging the matter locally.  as well, probably few people
are interested in helping you if you scold them.

of course, there is the option of hiring someone to work on this problem
for you, in which case you can treat them as befits the conventional (in
your business sphere) employer / employee relationship, and clearly set
out in a written contract.  you may consult the etc/SERVICES file to
find someone in your vicinity, or further away on the net.

thi






reply via email to

[Prev in Thread] Current Thread [Next in Thread]