help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug "Debugger entered--Lisp error: (void-function nil)"


From: newsspam5REMOVETHIS
Subject: Re: How to debug "Debugger entered--Lisp error: (void-function nil)"
Date: Sun, 08 Apr 2007 21:14:35 +0200
User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)

Tim X <timx@nospam.dev.null> writes:
[...]
>> The latest backtrace I get ... HTF can this happen in redisplay
>> ... the latest GNU Emacs from CVS is just compiling ... 
>>
>> Debugger entered--Lisp error: (void-function nil)
>>   (nil)
>>   redisplay()
>>   sit-for(5)
>>   vm-display-startup-message()
>>   byte-code("BYTE CODE REMOVED BY ME" [access-method folder vm-primary-inbox 
>> f vm-recognize-imap-maildrops vm-recognize-pop-maildrops string-match imap 
>> pop bufferp nil vm-pop-find-spec-for-name error "No such POP folder: %s" 
>> vm-pop-make-filename-for-spec t file-exists-p (rename-file f-pass f-nospec) 
>> ((error)) (rename-file f-nopass f-nospec) ((error)) 3 
>> vm-imap-parse-spec-to-list vm-imap-make-filename-for-spec expand-file-name 
>> file-directory-p "%s is a directory" vm-get-file-buffer no-conversion 
>> raw-text message "Reading %s..." find-file-noselect "Reading %s... done" 
>> (pop imap) buffer-name rename-buffer set-buffer-multibyte get-coding-system 
>> no-conversion-unix no-conversion-dos no-conversion-mac binary 
>> buffer-modified-p ((set-buffer-modified-p omodified)) encode-coding-region 
>> set-buffer-file-coding-system decode-coding-region coding-system-base 
>> raw-text-unix ...] 9)
>>   vm(nil nil)
>>   call-interactively(vm)
>>   command-execute(vm)
>>   command-line-1(("-eval" "(setq debug-on-error t)" "-f" "vm"))
>>   command-line()
>>   normal-top-level()
>
> What does that "BYTE-CODE REMOVED BY ME" mean?

Well, it means that I removed the binary garbage form the
backtrace ;-)

> I've not seen that before and
> that line doesn't look right. Maybe try something like M-x
> list-load-path-shadows just to be sure your loading what you think your
> loading. 

Unfortunately there are no load path shadows and no extra
packages loaded.

Thanks
Robert.

Attachment: backtrace
Description: The backtrace with byte code included ...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]