#1 fatal error

open
Jan Moringen
None
5
2009-07-04
2009-07-04
Otavio Salvador
No

Hello,

I've tried it and it fails with the bellow error:

if: Symbol's function definition is void: eieio-object-p

Discussion

  • Jan Moringen
    Jan Moringen
    2009-07-04

    The problem seems to be that the function `eieio-object-p' is not available when it is called. The only way I can imagine for this to happen is that the object system eieio (of the CEDET package) is not properly loaded. On the other hand, requiring eieio should have failed even earlier. Can you please provide more details on the circumstances under which the error appeared. Useful information would include the installation locations you used for CEDET and Rudel, a backtrace of the error (obtainable by running (setq debug-on-error t) or setting "Enter Debugger on Error" in the Options menu) and maybe the last few line of the *Messages* buffer. Thank you for your feedback.

     
  • Jan Moringen
    Jan Moringen
    2009-07-04

    • assigned_to: nobody --> scymtym
     
  • Hello,

    The first error I've solved updating cedet version. I was using sid's version (Debian) and it is not the latest.

    I've found other issues:

    - if emacs connects to another session and this closes the session, it has:

    Warning (emacs): #<rudel-obby-client-state-idle idle>: no method (rudel-dispatch-error: method-symbol-unbound): `rudel-obby/:- Peer has closed the GNUTLS connection'; arguments: nil

     
  • Jan Moringen
    Jan Moringen
    2009-07-05

    About the first issue (void function eieio-object-p):
    The INSTALL file states that it is necessary to use "the latest CVS version" of CEDET. That does not sound very attractive and actually is not really true any more. For the next release, I will update the INSTALL file to mention the CEDET release version that is required. With respect to this problem I would consider this issue solved.

    Connection termination error:
    The warning is harmless in principle but confusing and annoying. I will commit a fix to trunk as soon as I can.

     
  • Jan Moringen
    Jan Moringen
    2009-07-05

    There is a fix in svn trunk that should prevent the warning from appearing.