Eclipse Community Forums: C / C++ IDE (CDT) » Editor problem annotation for header files

Home » Language IDEs » C / C++ IDE (CDT) » Editor problem annotation for header files

Editor problem annotation for header files [message #204282]

Wed, 07 November 2007 09:10

Eclipse User

Hi,

CDT 4.0.1 has sometimes trouble with the indexer and doesn't support each
piece of code. In Editor -> Syntax Coloring I selected a red color for
Code->Problems and see some red strings.

I wonder how I can check the reason for it? I also activated "Enable editor
problem annotation", selected in Annotations yellow error markers to
display these and assumed that I just have to check these annotations to
find the cause of the trouble. Nevertheless I noticed that I also get red
marked code in files where no yellow editor problem is marked.

Maybe it is related to the fact the problems in included header files are
marked in the header file only and not additionally in each file including
it (in the #include line). Has this changed? In the past (CDT 4.0.0?) I
have seen a lot of problems including standard header files (<vector>, ...)
which vanished.

So how can I check where the trouble comes from (are all header files
found?, ...) without problem markers?
I read in this newsgroup about a logging method for the CDT parser but not
how to enable it. What config file do I have to edit? How?

Jens

Re: Editor problem annotation for header files [message #204290 is a reply to message #204282]

Wed, 07 November 2007 09:30

Eclipse User

Jens Seidel wrote:

> So how can I check where the trouble comes from (are all header files
> found?, ...) without problem markers?
> I read in this newsgroup about a logging method for the CDT parser but not
> how to enable it. What config file do I have to edit? How?

Oops, found it: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg08941.html

I created a file .eclipse/options with content

org.eclipse.cdt.core/debug/pdomtimings=true
org.eclipse.cdt.core/debug/indexer=true
org.eclipse.cdt.core/debug/indexer/activity=true
org.eclipse.cdt.core/debug/indexer/statistics=true
org.eclipse.cdt.core/debug/indexer/problems=true
org.eclipse.cdt.core/debug/parser=true
org.eclipse.cdt.core/debug/deltaprocessor=true
org.eclipse.cdt.core/debug/scanner=true
org.eclipse.cdt.core/debug/model=true

in my home directory and start eclipse with
eclipse -vmargs -Xms160m -Xmx768m -XX:MaxPermSize=128m -debug /home/jens/.eclipse/options
and get

Exception in thread "main"
java.lang.NoClassDefFoundError: /home/jens//eclipse/options

Note the wrong path!

Jens

Re: Editor problem annotation for header files [message #204385 is a reply to message #204290]

Thu, 08 November 2007 07:50

Eclipse User

Jens Seidel wrote:
> Jens Seidel wrote:
>
>> So how can I check where the trouble comes from (are all header files
>> found?, ...) without problem markers?
>> I read in this newsgroup about a logging method for the CDT parser but not
>> how to enable it. What config file do I have to edit? How?
>
> Oops, found it: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg08941.html
>
> I created a file .eclipse/options with content
>
> org.eclipse.cdt.core/debug/pdomtimings=true
> org.eclipse.cdt.core/debug/indexer=true
> org.eclipse.cdt.core/debug/indexer/activity=true
> org.eclipse.cdt.core/debug/indexer/statistics=true
> org.eclipse.cdt.core/debug/indexer/problems=true
> org.eclipse.cdt.core/debug/parser=true
> org.eclipse.cdt.core/debug/deltaprocessor=true
> org.eclipse.cdt.core/debug/scanner=true
> org.eclipse.cdt.core/debug/model=true
>
> in my home directory and start eclipse with
> eclipse -vmargs -Xms160m -Xmx768m -XX:MaxPermSize=128m -debug /home/jens/.eclipse/options
> and get
>
> Exception in thread "main"
> java.lang.NoClassDefFoundError: /home/jens//eclipse/options
>
> Note the wrong path!
>
> Jens

It should be
eclipse -debug /home/jens/.eclipse/options -vmargs -Xms160m -Xmx768m
-XX:MaxPermSize=128m

-vmargs must be the last option on the command line (everything
following it is passed to the Java VM).

--
Anton Leherbauer
Wind River CDT Team, Austria

Previous Topic:	Open Element (Ctrl + Shift + T) in debug perspective does not work
Next Topic:	No source available for main()

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 18:44:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter