all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Cc: samuel@ma.hw.ac.uk
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	[thread overview]
Message-ID: <3EBFC7DE.1000502@yahoo.co.uk> (raw)
In-Reply-To: <jk7k8wur3g.fsf@glug.org>

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 <hintak_leung@yahoo.co.uk> 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	other threads:[~2003-05-12 16:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 14:40 emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 15:22 ` Thien-Thi Nguyen
2003-05-12 16:12   ` Hin-Tak Leung [this message]
2003-05-12 17:18     ` emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.2) Thien-Thi Nguyen
2003-05-12 17:51       ` emacs-19.34 segfaults when built with Xfree 4.3.0(glibc2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 18:15         ` Thien-Thi Nguyen
2003-05-12 19:00           ` Hin-Tak Leung
2003-05-12 20:36             ` Thien-Thi Nguyen
2003-05-12 22:11               ` Hin-Tak Leung
     [not found]               ` <mailman.6068.1052777215.21513.help-gnu-emacs@gnu.org>
2003-05-13  7:07                 ` Kai Großjohann
     [not found] ` <20030512164103.1607f814.samuel@ma.hw.ac.uk>
2003-05-12 16:25   ` emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2) Hin-Tak Leung
     [not found]     ` <20030512180149.371bb9d5.samuel@ma.hw.ac.uk>
2003-05-12 17:29       ` Hin-Tak Leung
2003-05-12 22:41         ` Sam Halliday
2003-05-12 22:52           ` Hin-Tak Leung
2003-05-14  2:51         ` Eli Zaretskii
2003-05-14 13:48 ` Richard Stallman
2003-05-14 16:34   ` Hin-Tak Leung
2003-05-15 15:42     ` Richard Stallman
2003-05-15 18:27       ` Hin-Tak Leung
2003-05-16 10:38       ` Hin-Tak Leung
2003-05-16 11:40         ` Andreas Schwab
2003-05-16 12:11           ` Hin-Tak Leung
2003-05-16 12:40             ` Andreas Schwab
2003-05-16 17:11               ` Hin-Tak Leung
2003-05-17 13:50         ` Richard Stallman
2003-05-17 17:40           ` Hin-Tak Leung
  -- strict thread matches above, loose matches on Subject: below --
2003-06-29  7:57 emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.2) Tomoyuki Murakami

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EBFC7DE.1000502@yahoo.co.uk \
    --to=hintak_leung@yahoo.co.uk \
    --cc=samuel@ma.hw.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.