かわむらです。 2.6r4 -> 3.0へのアップグレード環境で、Wnn7 が xemacs 上で使えていません。 ＜症状＞ xemacs上で漢字変換すると、文字化けした文字が現れます(「^P・・・」 みたいに)。これで確定すると、xemacsごと「セグメンテーション違反です」 で落ちます。 このときのメッセージを添付しておきます。 kinput2を介して、漢字入力をすると正常に変換できます。 Cannaでは文字化けもなく、正常です。 さて、何か問題でしょうか？状況的には xemacs が問題な気がします。 内部の漢字コードの扱いが変わっている気がしますが、確信はありません。 3.0CRはまだのようですが、この辺は問題ないのでしょうか。 ＜環境＞ $ setime status 環境変数は ~/.vine/system/ime もしくは /etc/sysconfig/ime で設定されています. ----------------------------------------- [現在の漢字入力システム] wnn ----------------------------------------- [パッケージのインストール状況] [Canna] Canna-3.6p3-0vl8 [Wnn] package FreeWnn is not installed [Wnn7 server] wnn7-server-1.01-1vl25 [Wnn7 client] wnn7-xclients-1.02-3vl25 [Wnn6] package wnn6 is not installed [Atokx] package atokx is not installed [VJE-Delta] package vje-delta is not installed [Anthy] package anthy is not installed [UIM] package uim is not installed ----------------------------------------- [環境変数] EMACS_IME=wnn7 XIM_PROG=wnn7 CANNA_SERVER=unix JSERVER=localhost WNN7_FRONT_END=kinput2 WNN7_SERVER=localhost WNN6_FRONT_END=kinput2 WNN6_SERVER=localhost ----------------------------------------- xemacsのバージョンは、xemacs-21.4.15 です。
$ xemacs Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. Your version of XEmacs was distributed with a PROBLEMS file that may describe your crash, and with luck a workaround. Please check it first, but do report the crash anyway. Please report this bug by invoking M-x report-emacs-bug, or by selecting `Send Bug Report' from the Help menu. If necessary, send ordinary email to `crashes@xxxxxxxxxx'. *MAKE SURE* to include the XEmacs configuration from M-x describe-installation, or equivalently the file Installation in the top of the build tree. *Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely to be able to analyze the problem. Locate the core file produced as a result of this crash (often called `core' or `core.<process-id>', and located in the directory in which you started XEmacs or your home directory), and type gdb /usr/bin/xemacs core then type `where' at the debugger prompt. No GDB on your system? You may have DBX, or XDB, or SDB. (Ask your system administrator if you need help.) If no core file was produced, enable them (often with `ulimit -c unlimited' in case of future recurrance of the crash. Lisp backtrace follows: # bind (p r n proc) comm-wait-for-space(#<network connection "Wnn7" (22273 . "localhost") state:exit> 4) comm-unpack-u32() # bind (result egg-fixed-euc) # (unwind-protect ...) # bind (c env-id comm-accept-timeout zhuyin buffer proc context env) wnn7rpc-optimize-fi([#<network connection "Wnn7" (22273 . "localhost") state:exit> 0 kawamura [0 0]] ([-2 0 0 0 "" "" -2 -2 0] [-2 0 0 0 "" "" -2 -2 0] [2 75931 3 64974 "" "" -3 -3 6])) # bind (env context b bunsetsu-list) wnn7-optimize-in-server(([[#<network connection "Wnn7" ... state:exit> 0 kawamura ...] 3 2 75931 18 1 64974 2 1 5 271 "" "" "" 331 nil nil nil nil nil (... ...)])) # bind (env head) wnn7-server-hindo-update() #<compiled-function nil "...(119)" [egg:bunsetu-face-off egg:henkan-face-off nil wnn7-henkan-mode-in-use egg:*in-fence-mode* egg:*region-start* egg:*henkan-open* egg:*region-end* egg:*henkan-close* egg:*sai-henkan-start* egg-predict-status egg-predict-clear resume-undo-list 0 wnn7-bun-list max i egg:*old-bunsetu-suu* wnn7-server-bunsetu-kanji overwrite-mode undo-boundary egg:*sai-henkan-end* wnn7-server-hindo-update egg-predict-inc-kakutei-length wnn7-rensou-touroku egg-predict-toroku egg:quit-egg-mode run-hooks egg:henkan-end-hook] 4 nil nil>() call-interactively(wnn7-henkan-kakutei) # (condition-case ... . error) # (catch top-level ...) セグメンテーション違反です