Re: font locking problem

[Lowell Kirsh]

Alan Mackenzie wrote:
> Would you tell us your Emacs version number (M-x emacs-version) and your
> CC Mode version number (M-x c-version), please.

emacs-version: 21.3.1
c-version: 5.28

> That's an internal coding error, probably in CC Mode.  Try setting
> `debug-on-error'  (M-: (setq debug-on-error t)), then visit the file
> again.  That should give a stack dump.

Here's a stack dump:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  goto-char(nil)
  eval((goto-char (match-beginning 4)))
  font-lock-fontify-keywords-region(1 1515 t)
  font-lock-default-fontify-region(1 1515 t)
  font-lock-fontify-region(1 1515 t)
  byte-code("?Ã Ä?Åed	#?Æ ?Ç+Ã?" [save-match-data-internal verbose 
font-lock-fontified match-data ((set-match-data 
save-match-data-internal)) font-lock-fontify-region 
font-lock-after-fontify-buffer t] 4)
  font-lock-default-fontify-buffer()
  font-lock-fontify-buffer()
  font-lock-mode()
  turn-on-font-lock()
  turn-on-font-lock-if-enabled()
  global-font-lock-mode-buffers()
  run-hooks(find-file-hooks)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer FileTokenizer.java> 
"~/java/FileTokenizer.java" nil nil "~/java/FileTokenizer.java" (3385326 
775))
  find-file-noselect("~/java/FileTokenizer.java" nil nil 1)
  find-file("~/java/FileTokenizer.java" 1)
  call-interactively(find-file)


So, what should I do? Work around this error until the next version 
comes out? I'd rather do that than build from the newest cvs source 
(laziness).

Lowell