Thread View: fj.editor.xemacs
1 messages
1 total messages
Started by Shunichi Yamamoto
Wed, 06 Feb 2002 07:42
XEmacsがアボートして起動できない
Author: Shunichi Yamamoto
Date: Wed, 06 Feb 2002 07:42
Date: Wed, 06 Feb 2002 07:42
102 lines
5833 bytes
5833 bytes
みなさん、こんにちは。やまも2といいます。 Kondara MNU/Linux 2.1(RC2)を使用しているのですが以下のことで悩んでいま す。 XEmacs関係のパッケージをソースからコンパイルしてインストールしたのです がColor-mateをインストールしフォントをいくつかいじったところXEmacsが アボートしてしまい立ち上がらなくなります。 私がインストールしたのは以下のものです。 xemacs-21.4.6.tar.gz xemacs-21.4.6-info.tar.gz xemacs-21.4.6-elc.tar.gz xemacs-mule-sumo-2002-01-19.tar.bz2 xemacs-sumo-2002-01-19.tar.bz2 apel-200112050940.tar.gz slim-1_14-200202010558.tar.gz wemi-200108100955.tar.gz rail-1.2.5.tar.gz wl-2_8-200201071640.tar.gz color-mate-10.6.tar.gz とりあえず、上記のものをインストールしてColor-mateをインストールしなけ れば問題なくXEmacsは起動できます。 また、Color-mateで「color-mate-fontset-xemacs.el」内の「fontset-16」を 使用しようとするとアボートしてしまいます。また、それ以外でもフォントを 自分の好みのものに変更すると同様にアボートしてしまいます。 長くなってしまいますが、アボートしたときのエラーメッセージも載せておき ます。 ---- Fatal error: assertion failed, file xlwtabs.c, line 1997, *reply_width > 0 && *reply_height > 0 Fatal error (6). 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@xemacs.org'. *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/local/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: # (unwind-protect ...) # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x821bfb8) 0x827d518> ...) # (unwind-protect ...) # bind (inhibit-quit) # (unwind-protect ...) set-specifier-dirty-flag(#<gutter-specifier global=((... buffers-tab "\n") nil) fallback=#<gutter-specifier global=<unspecified> fallback=(...) 0x13a> 0x13c>) # bind (gutter-or-location) set-gutter-dirty-p(top) # bind (items force-selection frame) update-tab-in-gutter(#<x-frame "emacs" 0x26e2> t) #<compiled-function nil "...(29)" [gutter-buffers-tab-enabled add-hook create-frame-hook #<compiled-function ... "...(8)" ... 3> buffer-list-changed-hook update-tab-in-gutter default-gutter-position-changed-hook #<compiled-function nil "...(9)" ... 3> gutter-element-visibility-changed-hook #<compiled-function ... "...(14)" ... 3> selected-frame t] 3>() apply(#<compiled-function nil "...(29)" [gutter-buffers-tab-enabled add-hook create-frame-hook #<compiled-function ... "...(8)" ... 3> buffer-list-changed-hook update-tab-in-gutter default-gutter-position-changed-hook #<compiled-function nil "...(9)" ... 3> gutter-element-visibility-changed-hook #<compiled-function ... "...(14)" ... 3> selected-frame t] 3> nil) # (unwind-protect ...) (unwind-protect (apply (quote #<compiled-function nil "...(29)" ... 3>) args) (remove-hook (quote after-init-hook) (quote G82101) (quote nil))) # bind (args) G82101() run-hooks(G82101) load-init-file() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) アボートしました ---- Kondara2.0の時はこのようなことは無かったのですが、どうすれば回避できる のでしょうか? よろしくお願いします。 ---- やまも2=山本俊一でっす!! 『やまも2のPC奮闘体験語録』にいらしてください♪ URL http://members.jcom.home.ne.jp/1210329411/
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads