Byte-code interpreter error in latest 21.2

Hi, The latest version out of CVS didn't like my .emacs anymore. I've traced it down to (require eudc), but _only_ if I have my custom-declare-variables statement before it. With -debug-init, I get either: Signaling: (wrong-type-argument number-char-or-marker-p t) eudc-set-server("vb-mail1.corpemea.baynetworks.com" ph t) load-internal("~/.eudc-options" nil nil nil nil nil) load("~/.eudc-options") byte-code("..." [noninteractive locate-library eudc-options-file message "" featurep load infodock eudc-install-menu] 2) load-internal("eudc" nil t nil nil nil) load("eudc" nil t nil) require(eudc) load-internal("~/.emacs" t t t nil nil) load("~/.emacs" t t t) load-user-init-file("") load-init-file() command-line() normal-top-level() or Fatal error: assertion failed, file bytecode.c, line 1485, abort() Program received signal SIGABRT, Aborted. 0x4022c811 in __kill () (gdb) bt #0 0x4022c811 in __kill () #1 0x4022c63f in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x4022d84f in abort () at ../sysdeps/generic/abort.c:83 #3 0x8087dab in assert_failed (file=0x81a33e3 "bytecode.c", line=1485, expr=0x81a33ee "abort()") at emacs.c:2639 #4 0x8062064 in execute_rare_opcode (stack_ptr=0xbfffe6bc, program_ptr=0x8616eae "d\b\001", opcode=179) at bytecode.c:1485 #5 0x8060f10 in execute_optimized_program (program=0x8616ea0 ",j*\b\005", stack_depth=4, constants_data=0x85fe1a4) at bytecode.c:664 #6 0x8060a7d in funcall_compiled_function (fun=140499364, nargs=3, args=0xbfffe758) at bytecode.c:530 #7 0x808d40e in Feval (form=140827140) at eval.c:3045 #8 0x8111e81 in readevalloop (readcharfun=140602856, sourcename=140520320, evalfun=0x808c7a8 <Feval>, printflag=0) at lread.c:1454 #9 0x8110533 in Fload_internal (file=140520320, no_error=136510188, nomessage=136510188, nosuffix=136510188, codesys=136510188, used_codesys=136510188) at lread.c:743 #10 0x808dc67 in Ffuncall (nargs=7, args=0xbfffea68) at eval.c:3189 #11 0x8061160 in execute_optimized_program ( program=0x82eebe8 "À\t\n\013\fÅ\211&\006\207", stack_depth=7, constants_data=0x8366ba4) at bytecode.c:754 #12 0x8060a7d in funcall_compiled_function (fun=137757844, nargs=1, args=0xbfffeb80) at bytecode.c:530 depending on exactly what I have in my .emacs. According to bytecomp.el, opcode 179 is not used, and neither it nor bytecode.c have changed recently in a way that could cause this (as far as I can see, but I don't know that much about XEmacs internals). I have it trapped in gdb at the moment, so any suggestions would be much appreciated. Thanks Robert --