From: Russ Allbery <rra@stanford.edu>
Subject: Anyone using Oort with XEmacs 21.4.6?
Date: Wed, 26 Dec 2001 13:37:51 -0800 [thread overview]
Message-ID: <yladw5ek7k.fsf@windlord.stanford.edu> (raw)
I'm getting core dumps when using XEmacs 21.4.6. I'm likely to just
switch back to 21.1.12 for right now since 21.4.6 also has an annoying
performance regression when deleting text out of a font-lock buffer, but
I'm curious whether anyone else is seeing this one or if it's something
peculiar to my configuration.
It doesn't happen all the time, but about 25-50% of the time when starting
up a new XEmacs and going into Gnus I was getting a core dump.
Here's the Lisp backtrace:
# bind (form)
gnus-byte-compile((lambda (file orig-file) (nnmail-split-incoming file (quote nnml-save-mail) (quote nil) (if ... nil ...) (quote nnml-active-number))))
# bind (source incomings incoming total new i group-in fetching-sources sources spool-func group temp exit-func method)
nnmail-get-new-mail(nnml nnml-save-nov "~/Mail/" nil)
# bind (server group)
nnml-request-scan(nil "")
# bind (gnus-command-method gnus-inhibit-demon mail-source-plugged gnus-command-method group)
gnus-request-scan(nil (nnml ""))
# bind (where mesg force method)
gnus-read-active-file-1((nnml "") nil)
# (condition-case ... . ((quit (message "Quit reading the active file"))))
# (unwind-protect ...)
# bind (methods method not-native force)
gnus-read-active-file(nil nil)
# bind (init nnmail-fetched-sources dont-connect level rawfile)
gnus-setup-news(nil nil nil)
byte-code("..." [dont-connect did-connect gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-dribble-read-file gnus-use-grouplens bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil level gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook] 4)
# bind (level did-connect slave dont-connect arg)
gnus-1(nil nil nil)
# bind (slave dont-connect arg)
gnus(nil)
# bind (command-debug-status)
call-interactively(gnus)
# (condition-case ... . error)
# (catch top-level ...)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next reply other threads:[~2001-12-26 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 21:37 Russ Allbery [this message]
2001-12-26 22:18 ` Chris Halverson
2001-12-26 22:38 ` Karl Kleinpaste
2001-12-26 23:40 ` Russ Allbery
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=yladw5ek7k.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).