[debian-users:13290] [Q] XEmacs & Mew dies suddenly

[Masayuki Hatta <masayuki-h@xxxxxxxxxxxxxxx>]

八田(ま)です。

# ちょっとパニクっています。

XEmacs 上でしばらく Mew を使っていると、唐突に SEGV で死ぬように
なってしまいました。
大体 3-4 通のメールを読んだぐらいで必ず発生し、それなりに
再現性があるようです。

他にもこのような症状を経験された方はいらっしゃいませんか？
いらっしゃいましたら対策など教えて頂けると幸いです。

XEmacs が吐いたログを添付します。

Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.

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 as much configuration information as
possible; at the very least what OS and hardware you are running
on, and hopefully also what compiler and compiler options the
binary was compiled with, what options XEmacs was compiled with,
whether you are using a prebuilt binary from ftp.xemacs.org or
compiled XEmacs yourself for your system, etc.

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
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 as much configuration information as
possible; at the very least what OS and hardware you are running
on, and hopefully also what compiler and compiler options the
binary was compiled with, what options XEmacs was compiled with,
whether you are using a prebuilt binary from ftp.xemacs.org or
compiled XEmacs yourself for your system, etc.

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 XEmacs, 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:

  split-window(nil 8)
  # bind (msg-height sum-height winsum height msgwin obufwin windows action nbuf)
  mew-window-configure("+ml/debian-users" message)
  # (unwind-protect ...)
  # bind (next buf opart part ofld-msg msg fld)
  mew-summary-show()
  # bind (buf msg ofld-msg part opart)
  #<compiled-function (from "mew-summary.elc") nil "...(130)" [message "No message" mew-summary-message-number mew-syntax-number mew-current-get part opart ofld-msg msg buf (...) mew-window-configure mew-message-next-page 1 mew-summary-show] 6 ("/usr/share/xemacs20/site-lisp/mew/mew-summary.elc" . 26441) nil>()
  call-interactively(mew-summary-scroll-up)
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault

# 以前 Hamm で XEmacs や Mew を使っていたときはこんなこと無かったので、
# XEmacs のバグでは無いのではないかと思うのですが…

関係ありそうなパッケージは

ii  xemacs20-bin    20.4-13        Editor and kitchen sink -- support binaries
ii  xemacs20-mule-c 20.4-13        Editor and kitchen sink -- Mule binary com
ii  xemacs20-suppor 20.4-13        Editor and kitchen sink -- architecture in
ii  mew             1.93-2         Messaging in the Emacs World

--
八田真行 <masayuki-h@xxxxxxxxxxxxxxx>