From xemacs-m  Mon Feb 24 02:21:31 1997
Received: from ns.jsys.co.jp (root@ns.jsys.co.jp [202.33.240.82])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id CAA13230
	for <xemacs-beta@xemacs.org>; Mon, 24 Feb 1997 02:21:29 -0600 (CST)
Received: from cosmos.jsys.co.jp (root@cosmos.jsys.co.jp [172.31.80.5])
	by ns.jsys.co.jp (8.8.5/8.8.5) with ESMTP id RAA12457;
	Mon, 24 Feb 1997 17:21:26 +0900 (JST)
Received: from j-04110.jsys.co.jp (j-04110.jsys.co.jp [172.31.49.72])
	by cosmos.jsys.co.jp (8.8.5/8.8.5) with ESMTP id RAA19035;
	Mon, 24 Feb 1997 17:21:25 +0900 (JST)
Received: (from ienaga@localhost) by j-04110.jsys.co.jp (8.8.5/3.5Wpl2) id RAA09582; Mon, 24 Feb 1997 17:21:26 +0900 (JST)
Sender: ienaga@j-04110.jsys.co.jp
To: xemacs-beta@xemacs.org
Cc: Soren Dayton <csdayton@cs.uchicago.edu>
Subject: XEmacs 20.1-b2 and AUC TeX with Japanese filling
References: <m2wwrzhqyb.fsf@altair.xemacs.org> <xcdvi7ikjb8.fsf@jordan.cs.uchicago.edu> <rysbu9a52cu.fsf@skywalk.jsys.co.jp> <xcdpvxqkhwr.fsf@jordan.cs.uchicago.edu> <rysafou50fa.fsf@skywalk.jsys.co.jp> <xcdk9nykfsp.fsf@jordan.cs.uchicago.edu> <rys914e4y69.fsf@skywalk.jsys.co.jp> <xcdd8tqkd6j.fsf@jordan.cs.uchicago.edu>
Mime-Version: 1.0 (generated by tm-edit 7.101)
Content-Type: text/plain; charset=US-ASCII
From: Kazuyuki IENAGA <ienaga@jsys.co.jp>
Date: 24 Feb 1997 17:21:23 +0900
In-Reply-To: Soren Dayton's message of 23 Feb 1997 23:04:04 -0600
Message-ID: <rysiv3i4nss.fsf_-_@skywalk.jsys.co.jp>
Lines: 133
X-Mailer: Gnus v5.4.11/Emacs 19.34

I just compiled 20.1-b2 and test AUC TeX 9.7g.

Compiled XEmacs as follows:

# ./configure  --site-includes='/usr/local/include /usr/local/canna/include'
 --site-libraries=/usr/local/lib
 --with-mule --with-canna --with-sound=native

FreeBSD-2.2, xpm-3.4j, SWiM-2.0.
CFLAGS="-m486 -O2 -g"

Working fine, but generate core in AUC TeX mode.


The situation:

1.  In the AUC TeX mode with or *without* the load of tex-jp.el.
2.  When I converted Japanese Hiragata to Kanji using canna, at near
    end of the line and type <return> to cause auto-filling.


The reproducable steps:

1.  % xemacs -q -debug-init

2.  Load auc-tex (require auc-tex is installed)

    (if (locate-library "latex")
	(progn
	  (require 'tex-site)
	  (setq LaTeX-version "2")
	  ; (add-hook 'latex-mode-hook 'japanese-latex-mode) ; japanese
	  (setq auto-mode-alist
		(cons (cons "\\.tex$" 'latex-mode) auto-mode-alist))
	  ))

3.  Load canna library and init it
    (setq canna-server "localhost")
    (setq canna-file (expand-file-name "~/.canna")) ; optional
    (if (and (boundp 'CANNA) CANNA)
	(progn
	  (load-library "canna")
	  (canna)
	  (global-set-key "\C-\\" 'canna-toggle-japanese-mode))) ; opt

4.  Open new or existing LaTeX file.

5.  Set minor mode to auto-fill-mode (M-x auto-fill-mode).

6.  Input Japanese word, convert it, then type return to confirm the
    Japanese conversion result at near end of the line.
    The last character should be '.', '?' or ','.
    (Of course, Japanese period can be used substitute of '.')

Then get,

Fatal error: assertion failed, file regex.c, line 4572, VALID_CHARPTR_P (d)

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

Please report this bug to the address `crashes@xemacs.org'.
*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/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:

  re-search-forward("[^\\\\]%\\|\n\\|\\'")
  # (unwind-protect ...)
  # bind (count)
  # (unwind-protect ...)
  # (unwind-protect ...)
  TeX-brace-count-line()
  # (unwind-protect ...)
  LaTeX-indent-calculate-last()
  # (unwind-protect ...)
  LaTeX-indent-calculate()
  LaTeX-indent-line()
  indent-according-to-mode()
  # bind (comcol comstart soft)
  indent-new-comment-line()
  # (unwind-protect ...)
  # bind (prev-column fill-prefix fill-point give-up)
  do-auto-fill()
  # bind (ocolumn)
  canna:do-auto-fill()
  # bind (strs)
  canna:insert-fixed(19)
  # bind (strs)
  canna:display-candidates(19)
  # bind (arg ch)
  canna:functional-insert-command2(?\r 1)
  # bind (ch arg)
  canna-functional-insert-command(1)
  # bind (command-debug-status)
  call-interactively(canna-functional-insert-command)
  # (condition-case ... . error)
  # (catch top-level ...)
Abort (core dumped)

{ienaga@skywalk(126)}~% !gdb
gdb /usr/local/bin/xemacs-20.1-b2 xemacs-20.1-b2.core
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i386-unknown-freebsd), 
Copyright 1996 Free Software Foundation, Inc...
Core was generated by `xemacs-20.1-b2'.
Program terminated with signal 6, Abort trap.
Cannot access memory at address 0x102f5004.
#0  0x85f5821 in ?? ()Cannot access memory at address 0x102f5004.
(gdb) where
#0  0x85f5821 in ?? ()Cannot access memory at address 0x102f5004.
(gdb) q

