TAGS resolving to .c files in Windows

Has anyone else noticed that, in a native Win2K build ("XEmacs 21.4 (patch 6) \"Common Lisp (Windows)\" [Lucid] (i586-pc-win32) of Tue Dec 04 2001 on SHELTCPX"), attempting to find a tag which resolves to a .c file gets an error? Here's what I did: xemacs -vanilla M-. -> e:\acs\build\xemacs-windows-21.4-2001-12-04\TAGS -> gethash --> N ==> Wrong type argument: number-char-or-marker-p, 995\,30731 Here's the backtrace: Signaling: (wrong-type-argument number-char-or-marker-p 995\,30731) find-tag-internal("gethash") #<compiled-function (tagname &optional other-window) "...(80)" [result next tagname local-find-tag-hook find-tag-hook tag-buf find-tag-internal (find-tag find-tag-other-window tags-loop-continue) push-tag-mark pop-to-buffer t switch-to-buffer push-mark run-hooks find-tag nil tag-point last-command other-window tags-loop-scan tags-loop-operate] 4 ("e:\\XEmacs-21.4\\lisp\\etags.elc" . -16542) (byte-code "«'Á?ÂÃ!ÄD?" [current-prefix-arg ... find-tag-tag "Find tag: " nil] 2)>("gethash" nil) call-interactively(find-tag) Here's the relevant entry in the TAGS file: DEFUN ("gethash", Fgethash,gethash,
995,30731 Which seems OK. Now it turns out that elhash.c is loaded successfully, but it never gets made into the current buffer, nor is the jump to the proper place successful. Strangely enough, finding tags in .el files works. I'll try to investigate if I can find the time. - vin