[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debian-users:11430] Where is CORE.(XEmacs is down)



2,3回発生しているので、再現性はあるとおもうのですが
MewをXEmacsで使っていると突然落ちます。何かメッセージ
が出ていたので、scriptコマンドで拾っておきました。

たいていカーソルをマウスポインタで動かした後、SPCキィ
でメッセージを読もうとした時に発生するようです。

====================================================================================
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
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 5)
  # bind (msg-height sum-height winsum height msgwin obufwin windows action nbuf)
  mew-window-configure("+inbox" message)
  # (unwind-protect ...)
  # bind (next buf opart part ofld-msg msg fld)
  #<compiled-function (from "mew-summary.elc") nil "...(212)" [mew-summary-folder-name fld mew-summary-message-number msg mew-current-get message ofld-msg mew-syntax-number part opart buffer-name buf nil next mew-summary-toggle-disp-msg on (...) mew-window-configure mew-summary-display-message mew-message-next-page t mew-summary-display-part assoc mew-cache mew-decode-syntax "No message" set-buffer-modified-p] 4 ("/usr/share/xemacs20/site-lisp/mew/mew-summary.elc" . 17935) nil>()
  call-interactively(mew-summary-show)
  # (condition-case ... . error)
  # (catch top-level ...)
exit

Script done on Wed Dec 30 12:15:18 1998
===================================================================

で、coreファイルなんですが、カレントを探しても見付からないのですが
find / -name "core"などともしてみましたが、見付かるのは
/usr/src/kernel-source-2.0.34/net/core
find: /etc/ppp: Permission denied
find: /etc/chatscripts: Permission denied
find: /root: Permission denied
/dev/core
/proc/sys/net/core
find: /var/lib/xdm/authdir: Permission denied
find: /var/spool/cron/atjobs: Permission denied
find: /var/spool/cron/atspool: Permission denied
んな結果ばかり。coreはどこに?

===================================================================
こんな風になる前は、
ls -ls /var/lib/emacsen-common/installed-flavor
の内容がnullだったので、*.elファイルをload-path
で指定して、mewを走らせていました。が、速度面で
気に入らないので、スクリプトの内容を解析して、
installed-falvaorにxemacsという文字列を書き込ん
で、Mewをいったんremoveしてから再度 dpkg -i
しました。するとbytecompileがはじまったので
成功だとおもったのですが。

今、思うとbbdbの読み込みとかでエラーになって
いた記憶があります。やはり一度へんてこりんになった
のでXEmacs関連はやりなおしかなあ。

====+====+====+====+====+====+====+====+====+====+====+====+====+====+
yabuki yukiharu (矢吹幸治)
Email: yabuki@xxxxxxxxxxxxxxx
       GAA00412@xxxxxxxxxxx
PGP Key fingerprint = 27 96 DD BA FC FF BE 19  E5 60 2F 43 73 85 74 84
[debian-users:11194]で呼びかけたeamcs-commonのテスタ募集
====+====+====+====+====+====+====+====+====+====+====+====+====+====+