From: Thien-Thi Nguyen <ttn@glug.org>
Cc: samuel@ma.hw.ac.uk
Subject: Re: emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2)
Date: 12 May 2003 11:22:59 -0400 [thread overview]
Message-ID: <jk7k8wur3g.fsf@glug.org> (raw)
In-Reply-To: Hin-Tak Leung's message of "Mon, 12 May 2003 15:40:22 +0100"
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
next prev parent reply other threads:[~2003-05-12 15:22 UTC|newest]
Thread overview: 19+ 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 [this message]
2003-05-12 16:12 ` emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 17:18 ` 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
[not found] <mailman.5658.1052251660.21513.help-gnu-emacs@gnu.org>
2003-05-07 2:01 ` emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x, gcc 3.2) Sam Halliday
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 20:12 Hin-Tak Leung
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jk7k8wur3g.fsf@glug.org \
--to=ttn@glug.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).