From: Russ Allbery <rra@stanford.edu>
Subject: Re: Anyone using Oort with XEmacs 21.4.6?
Date: Wed, 26 Dec 2001 15:40:52 -0800 [thread overview]
Message-ID: <ylvget1rej.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <vxkofklk3p0.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Wed, 26 Dec 2001 17:38:03 -0500")
Karl Kleinpaste <karl@charcoal.com> writes:
> I regularly update to the latest beta or gamma XEmacs, and I keep very
> regularly updated in Oort Gnus. I last updated Oort this morning, and
> I'm running 21.4.6 under Linux RH7.1. No worries, for the most part;
> once in a blue moon, I get a coredump, but I have yet to trace it down
> to anything identifiable. That happens perhaps once a week. I have
> never seen a trace like the one you sent. What's your platform?
sparc-sun-solaris2.8 (64-bit kernel, but XEmacs was built 32-bit)
Built with gcc 2.95.3, linked against X11R6.4.3 (not vendor libraries)
Sounds like I should investigate further and try to get a C core dump and
then report it directly to the XEmacs folks. If I have time I'll do that,
but I'm not sure that I'll get a chance; I was seeing half-second delays
whenever I cut text out of a font-lock buffer (such as a message in
message mode) using 21.4.6, and that was so annoying that I would have
probably rolled back to 21.1.12 anyway. (Does anyone know if that's the
font-lock problem alluded to somewhat mysteriously in the release
announcement for 21.4.6?)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2001-12-26 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 21:37 Russ Allbery
2001-12-26 22:18 ` Chris Halverson
2001-12-26 22:38 ` Karl Kleinpaste
2001-12-26 23:40 ` Russ Allbery [this message]
2001-12-27 10:45 ` Russ Allbery
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=ylvget1rej.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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 NNTP newsgroup(s).