CEDET

Hello, 

I am using cedet for a rather large repository and I noticed that it works for some files but not for others. One of the files for which I cannot use ia-fast-jump at all has about 4.5K lines, and I wonder if this is the cause of the problem. 

I enabled some debug info (see below) and I understand that this file shows up as having no #include, but that is not true.

Moreover, if I delete the entire .semanticdb dir and try to jump to the definition of a symbol form this file, semantic immediately gives up and says it cannot find a suitable jump point. For the rest of the (smaller) files, it starts parsing. 

This seems to point out there a limit for the file size. Is this true?

Is there a way I can see more debug info?


Here is the debug info:
-----------------

Unable to find prefix KModule.

The prefix lookup code threw the following error:
  (error "Cannot find definition for \"KModule\"")

To debug this error you can do this:
  M-x toggle-debug-on-error RET   [ Do It ]
and then re-run the debug analyzer.


Local Scope Information:
 * Tag Class Constraint against SCOPE: nil
 * No known parents in current scope.
 * No known symbols currently in scope.
 * No known symbols declared locally.
No known possible completions.
When Semantic cannot find a symbol, it could be because the include
path was setup incorrectly.


Include Path Summary:

This file's project include search is handled by the EDE object:
  Buffer Target:  #<ede-cpp-root-target /home/zamf/esd/lib/Core/>
  Buffer Project: #<ede-cpp-root-project esd>
  Backup Locator: #<ede-locate-base Loc>


The system include path is:
  /usr/include
  /usr/local/include/
  /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include/
  /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/
  /usr/include/
  /usr/include/c++/4.4/
  /usr/include/c++/4.4/x86_64-linux-gnu/
  /usr/include/c++/4.4/backward/


Include Summary: /home/zamf/esd/lib/Core/Executor.cpp

Executor.cpp contains 0 includes.

 No unknown includes.


This is the project configuration 

(ede-cpp-root-project "esd"                                                                                                                                                                                                                 
                :name "esd"                                                                                                                                                                                                                 
                :file "~/esd/Makefile"                                                                                                                                                                                                      
                :include-path '("/"                                                                                                                                                                                                         
                                "/include"                                                                                                                                                                                                  
                                )                                                                                                                                                                                                           
                :system-include-path '("/usr/include/"                                                                                                                                                                                      
                                       "~/llvm/llvm-2.6/include")                                                                                                                                                                          
                :spp-table '(("isUnix" . "")                                                                                                                                                                                               
                             ("BOOST_TEST_DYN_LINK" . "")))

Thanks, 
Cristi

Re: [CEDET-devel] problem analyzing large file From: Eric M. Ludlam <eric@si...> - 2010-08-14 14:06 The only thing I can think of is that you may have never given Emacs enough time to parse your super-large file, or the file has some sort of #ifdef syntax at the beginning of the file that may not be properly balanced, thus ifdef'ing out the whole file. Most buffers are parsed in idle time. If you press a key it is supposed to cancel the parsing to allow emacs to be more responsive. If a parse takes 1 minute, but you never wait that long, it won't finish. In the senator menu, choose "Force Tag Refresh" to parse the file. The command M-x bovinate RET will dump the raw tag list if you need to inspect it. Eric On 08/13/2010 05:35 AM, Cristian Zamfir wrote: > > Hello, > > I am using cedet for a rather large repository and I noticed that it works for some files but not for others. One of the files for which I cannot use ia-fast-jump at all has about 4.5K lines, and I wonder if this is the cause of the problem. > > I enabled some debug info (see below) and I understand that this file shows up as having no #include, but that is not true. > > Moreover, if I delete the entire .semanticdb dir and try to jump to the definition of a symbol form this file, semantic immediately gives up and says it cannot find a suitable jump point. For the rest of the (smaller) files, it starts parsing. > > This seems to point out there a limit for the file size. Is this true? > > Is there a way I can see more debug info? > > > Here is the debug info: > ----------------- > > Unable to find prefix KModule. > > The prefix lookup code threw the following error: > (error "Cannot find definition for \"KModule\"") > > To debug this error you can do this: > M-x toggle-debug-on-error RET [ Do It ] > and then re-run the debug analyzer. > > > Local Scope Information: > * Tag Class Constraint against SCOPE: nil > * No known parents in current scope. > * No known symbols currently in scope. > * No known symbols declared locally. > No known possible completions. > When Semantic cannot find a symbol, it could be because the include > path was setup incorrectly. > > > Include Path Summary: > > This file's project include search is handled by the EDE object: > Buffer Target: #<ede-cpp-root-target /home/zamf/esd/lib/Core/> > Buffer Project: #<ede-cpp-root-project esd> > Backup Locator: #<ede-locate-base Loc> > > > The system include path is: > /usr/include > /usr/local/include/ > /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include/ > /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/ > /usr/include/ > /usr/include/c++/4.4/ > /usr/include/c++/4.4/x86_64-linux-gnu/ > /usr/include/c++/4.4/backward/ > > > Include Summary: /home/zamf/esd/lib/Core/Executor.cpp > > Executor.cpp contains 0 includes. > > No unknown includes. > > > This is the project configuration > > (ede-cpp-root-project "esd" > :name "esd" > :file "~/esd/Makefile" > :include-path '("/" > "/include" > ) > :system-include-path '("/usr/include/" > "~/llvm/llvm-2.6/include") > :spp-table '(("isUnix" . "") > ("BOOST_TEST_DYN_LINK" . ""))) > > Thanks, > Cristi > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Cedet-devel mailing list > Cedet-devel@... > https://lists.sourceforge.net/lists/listinfo/cedet-devel >

Re: [CEDET-devel] problem analyzing large file From: Cristian Zamfir <cristian.zamfir@ep...> - 2010-08-16 14:55 Thanks Eric, senator tag refresh fixed the problem. Cristi On Aug 14, 2010, at 4:06 PM, Eric M. Ludlam wrote: > The only thing I can think of is that you may have never given Emacs enough time to parse your super-large file, or the file has some sort of #ifdef syntax at the beginning of the file that may not be properly balanced, thus ifdef'ing out the whole file. > > Most buffers are parsed in idle time. If you press a key it is supposed to cancel the parsing to allow emacs to be more responsive. If a parse takes 1 minute, but you never wait that long, it won't finish. > > In the senator menu, choose "Force Tag Refresh" to parse the file. The command > > M-x bovinate RET > > will dump the raw tag list if you need to inspect it. > > Eric > > On 08/13/2010 05:35 AM, Cristian Zamfir wrote: >> >> Hello, >> >> I am using cedet for a rather large repository and I noticed that it works for some files but not for others. One of the files for which I cannot use ia-fast-jump at all has about 4.5K lines, and I wonder if this is the cause of the problem. >> >> I enabled some debug info (see below) and I understand that this file shows up as having no #include, but that is not true. >> >> Moreover, if I delete the entire .semanticdb dir and try to jump to the definition of a symbol form this file, semantic immediately gives up and says it cannot find a suitable jump point. For the rest of the (smaller) files, it starts parsing. >> >> This seems to point out there a limit for the file size. Is this true? >> >> Is there a way I can see more debug info? >> >> >> Here is the debug info: >> ----------------- >> >> Unable to find prefix KModule. >> >> The prefix lookup code threw the following error: >> (error "Cannot find definition for \"KModule\"") >> >> To debug this error you can do this: >> M-x toggle-debug-on-error RET [ Do It ] >> and then re-run the debug analyzer. >> >> >> Local Scope Information: >> * Tag Class Constraint against SCOPE: nil >> * No known parents in current scope. >> * No known symbols currently in scope. >> * No known symbols declared locally. >> No known possible completions. >> When Semantic cannot find a symbol, it could be because the include >> path was setup incorrectly. >> >> >> Include Path Summary: >> >> This file's project include search is handled by the EDE object: >> Buffer Target: #<ede-cpp-root-target /home/zamf/esd/lib/Core/> >> Buffer Project: #<ede-cpp-root-project esd> >> Backup Locator: #<ede-locate-base Loc> >> >> >> The system include path is: >> /usr/include >> /usr/local/include/ >> /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include/ >> /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/ >> /usr/include/ >> /usr/include/c++/4.4/ >> /usr/include/c++/4.4/x86_64-linux-gnu/ >> /usr/include/c++/4.4/backward/ >> >> >> Include Summary: /home/zamf/esd/lib/Core/Executor.cpp >> >> Executor.cpp contains 0 includes. >> >> No unknown includes. >> >> >> This is the project configuration >> >> (ede-cpp-root-project "esd" >> :name "esd" >> :file "~/esd/Makefile" >> :include-path '("/" >> "/include" >> ) >> :system-include-path '("/usr/include/" >> "~/llvm/llvm-2.6/include") >> :spp-table '(("isUnix" . "") >> ("BOOST_TEST_DYN_LINK" . ""))) >> >> Thanks, >> Cristi >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Cedet-devel mailing list >> Cedet-devel@... >> https://lists.sourceforge.net/lists/listinfo/cedet-devel >>

Re: [CEDET-devel] problem analyzing large file From: Richard Kim <emacs18@gm...> - 2010-09-04 03:52 I would just like to point out that semantic has no problem with C/C++ files with 20k lines. semantic-force-refresh almost always finishes within a second. I don't think I've seen it take longer then 3 seconds. Some files have functions with many thousands of lines each. Semantic has no problem with these either. I've seen `M-x bovinate RET' take almost 30 seconds of some of the largest files though, but this is not due to parsing time but more it seem to be due to formatting and printing the data. This is on a fast machine with lots of memory though. -----Original Message----- From: Eric M. Ludlam <eric@...> To: Cristian Zamfir <cristian.zamfir@...> Cc: cedet-devel@... Subject: Re: [CEDET-devel] problem analyzing large file Date: Sat, 14 Aug 2010 10:06:09 -0400 The only thing I can think of is that you may have never given Emacs enough time to parse your super-large file, or the file has some sort of #ifdef syntax at the beginning of the file that may not be properly balanced, thus ifdef'ing out the whole file. Most buffers are parsed in idle time. If you press a key it is supposed to cancel the parsing to allow emacs to be more responsive. If a parse takes 1 minute, but you never wait that long, it won't finish. In the senator menu, choose "Force Tag Refresh" to parse the file. The command M-x bovinate RET will dump the raw tag list if you need to inspect it. Eric On 08/13/2010 05:35 AM, Cristian Zamfir wrote: > > Hello, > > I am using cedet for a rather large repository and I noticed that it works for some files but not for others. One of the files for which I cannot use ia-fast-jump at all has about 4.5K lines, and I wonder if this is the cause of the problem. > > I enabled some debug info (see below) and I understand that this file shows up as having no #include, but that is not true. > > Moreover, if I delete the entire .semanticdb dir and try to jump to the definition of a symbol form this file, semantic immediately gives up and says it cannot find a suitable jump point. For the rest of the (smaller) files, it starts parsing. > > This seems to point out there a limit for the file size. Is this true? > > Is there a way I can see more debug info? > > > Here is the debug info: > ----------------- > > Unable to find prefix KModule. > > The prefix lookup code threw the following error: > (error "Cannot find definition for \"KModule\"") > > To debug this error you can do this: > M-x toggle-debug-on-error RET [ Do It ] > and then re-run the debug analyzer. > > > Local Scope Information: > * Tag Class Constraint against SCOPE: nil > * No known parents in current scope. > * No known symbols currently in scope. > * No known symbols declared locally. > No known possible completions. > When Semantic cannot find a symbol, it could be because the include > path was setup incorrectly. > > > Include Path Summary: > > This file's project include search is handled by the EDE object: > Buffer Target: #<ede-cpp-root-target /home/zamf/esd/lib/Core/> > Buffer Project: #<ede-cpp-root-project esd> > Backup Locator: #<ede-locate-base Loc> > > > The system include path is: > /usr/include > /usr/local/include/ > /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include/ > /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/ > /usr/include/ > /usr/include/c++/4.4/ > /usr/include/c++/4.4/x86_64-linux-gnu/ > /usr/include/c++/4.4/backward/ > > > Include Summary: /home/zamf/esd/lib/Core/Executor.cpp > > Executor.cpp contains 0 includes. > > No unknown includes. > > > This is the project configuration > > (ede-cpp-root-project "esd" > :name "esd" > :file "~/esd/Makefile" > :include-path '("/" > "/include" > ) > :system-include-path '("/usr/include/" > "~/llvm/llvm-2.6/include") > :spp-table '(("isUnix" . "") > ("BOOST_TEST_DYN_LINK" . ""))) > > Thanks, > Cristi > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Cedet-devel mailing list > Cedet-devel@... > https://lists.sourceforge.net/lists/listinfo/cedet-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Cedet-devel mailing list Cedet-devel@... https://lists.sourceforge.net/lists/listinfo/cedet-devel

1 message has been excluded from this view by a project administrator.