CEDET

On 09/30/2012 11:23 AM, Laurynas Biveinis wrote:
> Hi -
>
> I'm trying to set up CEDET but am stuck with $SUBJECT.
>
> My project config is:
>
> (ede-cpp-root-project "mysql-5.5"
>   :name "MySQL 5.5"
>   :file "~/percona/src/5.5/CMakeLists.txt"
>   :spp-table '(("HAVE_CONFIG_H" . ""))
>   :include-path '("/sql"
>                   "/include"
>                   "/storage/innobase/include"))
>
> Whenever I open a source file in this project and try to invoke
> semantic-c-describe-environment, it fails with
>
> eieio-generic-call-primary-only: Method object-print called on nil

Could you provide a stack by setting:

M-x toggle-debug-on-error RET

which will get you a backtrace.  There are several calls to 
object-print, and I'm curious which one it is.

Thanks!
Eric

Hi -

>> Whenever I open a source file in this project and try to invoke
>> semantic-c-describe-environment, it fails with
>>
>> eieio-generic-call-primary-only: Method object-print called on nil
>
>
> Could you provide a stack by setting:
>
> M-x toggle-debug-on-error RET
>
> which will get you a backtrace.  There are several calls to object-print,
> and I'm curious which one it is.

With this one I got

Debugger entered--Lisp error: (error "Method object-print called on nil")
  signal(error ("Method object-print called on nil"))
  error("Method %s called on nil" object-print)
  eieio-generic-call-primary-only(object-print (nil))
  object-print(nil)
  semantic-c-describe-environment()
  call-interactively(semantic-c-describe-environment t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)

Which I don't think narrows it down it much. I tried edebug and it
showed the error on

      (princ "\n\nMacro Summary:\n")
      (when semantic-lex-c-preprocessor-symbol-file
	(princ "\n  Your CPP table is primed from these files:\n")
	(dolist (file semantic-lex-c-preprocessor-symbol-file)
	  (princ "    ")
	  (princ file)
	  (princ "\n")
	  (princ "    in table: ")
	  (princ (object-print (semanticdb-file-table-object file)))
	  (princ "\n")
	  ))

file was "/usr/include/cdefs.h", and semanticdb-file-table-object
returned nil for it.

Thanks,
-- 
Laurynas

Ping?

2012/10/4 Laurynas Biveinis <laurynas.biveinis@...>:
> Hi -
>
>>> Whenever I open a source file in this project and try to invoke
>>> semantic-c-describe-environment, it fails with
>>>
>>> eieio-generic-call-primary-only: Method object-print called on nil
>>
>>
>> Could you provide a stack by setting:
>>
>> M-x toggle-debug-on-error RET
>>
>> which will get you a backtrace.  There are several calls to object-print,
>> and I'm curious which one it is.
>
> With this one I got
>
> Debugger entered--Lisp error: (error "Method object-print called on nil")
>   signal(error ("Method object-print called on nil"))
>   error("Method %s called on nil" object-print)
>   eieio-generic-call-primary-only(object-print (nil))
>   object-print(nil)
>   semantic-c-describe-environment()
>   call-interactively(semantic-c-describe-environment t nil)
>   execute-extended-command(nil)
>   call-interactively(execute-extended-command nil nil)
>
> Which I don't think narrows it down it much. I tried edebug and it
> showed the error on
>
>       (princ "\n\nMacro Summary:\n")
>       (when semantic-lex-c-preprocessor-symbol-file
>         (princ "\n  Your CPP table is primed from these files:\n")
>         (dolist (file semantic-lex-c-preprocessor-symbol-file)
>           (princ "    ")
>           (princ file)
>           (princ "\n")
>           (princ "    in table: ")
>           (princ (object-print (semanticdb-file-table-object file)))
>           (princ "\n")
>           ))
>
> file was "/usr/include/cdefs.h", and semanticdb-file-table-object
> returned nil for it.
>
> Thanks,
> --
> Laurynas



-- 
Laurynas

Laurynas Biveinis writes:
> Ping?

I'm afraid I can't really help you with that. For some reason cdefs.h
cannot be parsed. The only advice I can give you is to update to latest
CEDET from bzr and see if that fixes it. See

http://cedet.sourceforge.net/bzr-repo.shtml

for details on how to get it.

-David

Hi Laurynas,

I'm going to guess that your cdefs.h has no database associated with it.

Perhaps that bit of code you identified should really read:

       (princ "\n\nMacro Summary:\n")
       (when semantic-lex-c-preprocessor-symbol-file
	(princ "\n  Your CPP table is primed from these files:\n")
	(dolist (file semantic-lex-c-preprocessor-symbol-file)
	  (princ "    ")
	  (princ file)
	  (princ "\n")
	  (princ "    in table: ")
	  (let ((fto (semanticdb-file-table-object file)))
	    (if fto
		(princ (object-print fto))
	      (princ "No Table")))
	  (princ "\n")
	  ))

because this is a reasonable thing if someone were to add such bad files 
in by accident through configuration.  I'm not sure what other 
consequences there are to bogus preprocessor symbol files though.

Does your /usr/include/cdefs.h file really exist?  Are there symlinks or 
other weirdness of file-system out there?

Eric

On 10/04/2012 12:44 AM, Laurynas Biveinis wrote:
> Hi -
>
>>> Whenever I open a source file in this project and try to invoke
>>> semantic-c-describe-environment, it fails with
>>>
>>> eieio-generic-call-primary-only: Method object-print called on nil
>>
>>
>> Could you provide a stack by setting:
>>
>> M-x toggle-debug-on-error RET
>>
>> which will get you a backtrace.  There are several calls to object-print,
>> and I'm curious which one it is.
>
> With this one I got
>
> Debugger entered--Lisp error: (error "Method object-print called on nil")
>    signal(error ("Method object-print called on nil"))
>    error("Method %s called on nil" object-print)
>    eieio-generic-call-primary-only(object-print (nil))
>    object-print(nil)
>    semantic-c-describe-environment()
>    call-interactively(semantic-c-describe-environment t nil)
>    execute-extended-command(nil)
>    call-interactively(execute-extended-command nil nil)
>
> Which I don't think narrows it down it much. I tried edebug and it
> showed the error on
>
>        (princ "\n\nMacro Summary:\n")
>        (when semantic-lex-c-preprocessor-symbol-file
> 	(princ "\n  Your CPP table is primed from these files:\n")
> 	(dolist (file semantic-lex-c-preprocessor-symbol-file)
> 	  (princ "    ")
> 	  (princ file)
> 	  (princ "\n")
> 	  (princ "    in table: ")
> 	  (princ (object-print (semanticdb-file-table-object file)))
> 	  (princ "\n")
> 	  ))
>
> file was "/usr/include/cdefs.h", and semanticdb-file-table-object
> returned nil for it.
>
> Thanks,

Hi Eric -

There is no /usr/include/cdefs.h on my system, and as far as I can
tell, it's not supposed to be there neither. There are
/usr/include/x86_64-linux-gnu/sys/cdefs.h
/usr/include/sys/cdefs.h
instead.

I guess I should find out what makes CEDET think that there should be one?

Thanks,
Laurynas

2012/11/23 Eric M. Ludlam <eric@...>:
> Hi Laurynas,
>
> I'm going to guess that your cdefs.h has no database associated with it.
>
> Perhaps that bit of code you identified should really read:
>
>
>       (princ "\n\nMacro Summary:\n")
>       (when semantic-lex-c-preprocessor-symbol-file
>         (princ "\n  Your CPP table is primed from these files:\n")
>         (dolist (file semantic-lex-c-preprocessor-symbol-file)
>           (princ "    ")
>           (princ file)
>           (princ "\n")
>           (princ "    in table: ")
>           (let ((fto (semanticdb-file-table-object file)))
>             (if fto
>                 (princ (object-print fto))
>               (princ "No Table")))
>           (princ "\n")
>           ))
>
> because this is a reasonable thing if someone were to add such bad files in
> by accident through configuration.  I'm not sure what other consequences
> there are to bogus preprocessor symbol files though.
>
> Does your /usr/include/cdefs.h file really exist?  Are there symlinks or
> other weirdness of file-system out there?
>
> Eric
>
>
> On 10/04/2012 12:44 AM, Laurynas Biveinis wrote:
>>
>> Hi -
>>
>>>> Whenever I open a source file in this project and try to invoke
>>>> semantic-c-describe-environment, it fails with
>>>>
>>>> eieio-generic-call-primary-only: Method object-print called on nil
>>>
>>>
>>>
>>> Could you provide a stack by setting:
>>>
>>> M-x toggle-debug-on-error RET
>>>
>>> which will get you a backtrace.  There are several calls to object-print,
>>> and I'm curious which one it is.
>>
>>
>> With this one I got
>>
>> Debugger entered--Lisp error: (error "Method object-print called on nil")
>>    signal(error ("Method object-print called on nil"))
>>    error("Method %s called on nil" object-print)
>>    eieio-generic-call-primary-only(object-print (nil))
>>    object-print(nil)
>>    semantic-c-describe-environment()
>>    call-interactively(semantic-c-describe-environment t nil)
>>    execute-extended-command(nil)
>>    call-interactively(execute-extended-command nil nil)
>>
>> Which I don't think narrows it down it much. I tried edebug and it
>> showed the error on
>>
>>        (princ "\n\nMacro Summary:\n")
>>        (when semantic-lex-c-preprocessor-symbol-file
>>         (princ "\n  Your CPP table is primed from these files:\n")
>>         (dolist (file semantic-lex-c-preprocessor-symbol-file)
>>           (princ "    ")
>>           (princ file)
>>           (princ "\n")
>>           (princ "    in table: ")
>>           (princ (object-print (semanticdb-file-table-object file)))
>>           (princ "\n")
>>           ))
>>
>> file was "/usr/include/cdefs.h", and semanticdb-file-table-object
>> returned nil for it.
>>
>> Thanks,



-- 
Laurynas