From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: How to correct ? Error Messages
Date: 11 Nov 1999 18:03:53 -0500 [thread overview]
Message-ID: <5b7ljoy6jq.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Pieter Wenk's message of "Thu, 11 Nov 1999 09:07:38 +0100"
Please check `gnus-newsgroup-adaptive-score-file'. The default value
is nil.
And it is also a bug of Emacs, since it crashed.
--
Shenghuo ZHU
>>>>> "Pieter" == Pieter Wenk <pwenk@urbanet.ch> writes:
Pieter> Hello to all:
Pieter> I have a problem with 2 NG. When quitting with "c", I am
Pieter> getting:
Pieter> then type `where' when the debugger prompt comes up.
Pieter> (If you don't have GDB on your system, you might have DBX,
Pieter> or XDB, or SDB. A similar procedure should work for all of
Pieter> these. Ask your system administrator if you need more help.)
Pieter> Lisp backtrace follows:
Pieter> # (unwind-protect ...)
Pieter> insert-file-contents-internal("/home/p.wenk/News/" nil nil nil nil undecided used-codesys)
Pieter> byte-code("ÀÁ\n
Pieter> #
Pieter> ®`ÅÆ\n
Pieter> #® \n!®® \n:«\n
Pieter> ª \n!¬ \n\" \nÐ\n
Pieter> \nÔ&
Pieter> À" [run-hook-with-args insert-file-contents-access-hook filename visit coding-system-for-read run-special-hook-with-args insert-file-contents-pre-hook find-file-coding-system-for-read-from-filename buffer-file-coding-system-for-read no-conversion coding-system return-val find-coding-system message "Invalid coding-system (%s), using 'undecided" undecided insert-file-contents-internal beg end replace used-codesys] 9)
Pieter> # (condition-case ... . ((file-error (byte-code "ÀÁ\n
Pieter> $
Pieter> @
Pieter> A\"" ... 5))))
Pieter> # bind (return-val coding-system used-codesys conversion-func replace end beg visit filename)
Pieter> insert-file-contents("/home/p.wenk/News/")
Pieter> # (unwind-protect ...)
Pieter> # bind (alist file)
Pieter> gnus-score-load-score-alist("/home/p.wenk/News/")
Pieter> # bind (alist lists global cached file file)
Pieter> gnus-score-load-file("")
Pieter> # (unwind-protect ...)
Pieter> gnus-score-adaptive()
Pieter> # bind (headers group)
Pieter> # (unwind-protect ...)
Pieter> # bind (non-destructive)
Pieter> gnus-summary-update-info()
Pieter> # bind (buf group-point mode quit-config group temporary)
Pieter> gnus-summary-exit()
Pieter> # bind (quietly all)
Pieter> gnus-summary-catchup-and-exit(nil)
Pieter> # bind (command-debug-status)
Pieter> call-interactively(gnus-summary-catchup-and-exit)
Pieter> # bind (obuf owin opoint func in-buffer nosaves nosave-but-article nosave-in-article keys not-restore-window key arg)
Pieter> gnus-article-read-summary-keys(nil)
Pieter> # bind (command-debug-status)
Pieter> call-interactively(gnus-article-read-summary-keys)
Pieter> # (condition-case ... . error)
Pieter> # (catch top-level ...)
Pieter> Erreur de segmentation.
Pieter> p.wenk@sre-4-139:~ >
Pieter> What's all this ?
Pieter> Many thanks for your help
Pieter> Regards
Pieter> --
Pieter> / / (_)____ __ ____ __
Pieter> Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
Pieter> /____/_/_//_/\_,_/ /_/\_\
prev parent reply other threads:[~1999-11-11 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-11 8:07 Pieter Wenk
1999-11-11 23:03 ` Shenghuo ZHU [this message]
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=5b7ljoy6jq.fsf@giga.cs.rochester.edu \
--to=zsh@cs.rochester.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).