[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[debian-users:27960] XEmacs + Wanderlust でセグメンテーション違反
testing/unstableを使っているのですが、2日ほど前にupgradeしてからXEmacs
上のWanderlustで未読メールを読もうとするとXEmacsがセグメンテーション違反で
落ちるようになってしまいました。Emacsではまったく問題ありません。
その時のエラーメッセージは以下のようなものです。
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes@xxxxxxxxxx'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
put-database("<200011190922.FMLAAB11252.rc5-ml@xxxxxxxxxxx>" "(\"%rc5-ml:puppe t/cram-md5@mirage:993!\" 1)" #<database "/home/puppet/.elmo/msgid" (berkeley-db/ hash/writeonly) 0x5d75>)
# bind (db number folder msgid)
elmo-database-msgid-put("<200011190922.FMLAAB11252.rc5-ml@xxxxxxxxxxx>" "%rc5- ml:puppet/cram-md5@mirage:993!" 1)
# bind (importants unreads msgs expunged mark update-top-list update-thread cr ossed2 crossed ret-val entity overview-append curp in-db in-folder gc-message re sult num i has-nntp delete-list append-list initial-append-list diff buffer-read -only inhibit-read-only elmo-mime-charset case-fold-search overview mark-alist n umber-alist cur-buf folder sync-all unset-cursor seen-list)
wl-summary-sync-update3(nil unset-cursor)
# (unwind-protect ...)
# bind (msgdb-dir type ret-val seen-list unset-cursor)
wl-summary-sync-force-update(unset-cursor)
# bind (wl-summary-highlight wl-use-scoring)
# (unwind-protect ...)
byte-code("..." [t update nil end re-search-forward "^ *[0-9]+[^0-9]" 0 1 wl-g et-assoc-list-value wl-summary-number-column-alist wl-summary-buffer-folder-name wl-summary-default-number-column wl-summary-buffer-number-column wl-repeat-stri ng "." wl-summary-buffer-number-regexp wl-summary-disp-msg fld reuse-buf keep-cu rsor wl-summary-highlight hilit ((byte-code A+AA\n!A*\nqAC
!A+AE A,AFAG!AH AI!AJAK!ebALAG!A+A!AMANAO !\"A+ A+ASA*A,AU)A*dbAV!A+AXyA*AY AU ,A+A( A,A$A+A^ed\"VA+
A.[yA``d\")A*A`ed\"!A,AbAc
!$AeAf$GAK$$$)!!ASaA+Ag (A+ AiAj(\"A+
+A+ AlAm AnZAnA%!AK" ... 7)) scoring interactive wl-use-scoring sca n-type wl-ask-range folder intern elmo-folder-plugged-p wl-folder-sync-range-ali st wl-default-sync-range wl-summary-sync unset-cursor all "all" no-sync force-up date wl-summary-sync-force-update mes] 4)
# bind (entity retval reuse-buf hilit mes buf cur-fld fld keep-cursor scoring interactive sticky other-window scan-type folder)
wl-summary-goto-folder-subr("%rc5-ml:puppet/cram-md5@mirage:993!" update nil n il t)
# bind (summary-buf error-selecting entity beg end indent opened fname err fld -name arg)
wl-folder-jump-to-current-entity(nil)
# bind (command-debug-status)
call-interactively(wl-folder-jump-to-current-entity)
# (condition-case ... . error)
# (catch top-level ...)
セグメンテーション違反です
Lispは良くわからないので結局のところWanderlustのバグなのかXEmacsのバグ
なのかすら不明です。何か対処法を知っている方がいましたら教えてください。
お願いします。