This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 245306 - NB8.0 Patch 2 broke code assistance
Summary: NB8.0 Patch 2 broke code assistance
Status: RESOLVED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Project Discovery (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-29 18:37 UTC by -eki
Modified: 2014-07-23 17:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stacktrace (3.41 KB, application/octet-stream)
2014-06-29 18:37 UTC, -eki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description -eki 2014-06-29 18:37:26 UTC
Created attachment 147819 [details]
Stacktrace

Patch 2 of Netbeans 8.0 broke the code assistance for C(++) projects. All identifiers are marked as error, navigation to source etc. isn't working too.

Problems:
---------

 1. Navigation Source -> Header / Header -> Source not working
 2. All identifier (Methods, variables etc.) are marked as an error
 3. ClassCastException is thrown (especially if "Code Assistance -> Reparse Project" is used) - please see attached stacktrace
 4. No linking of source / header in editor

Still working:
--------------

 1. Codecompletion
 2. Compilation

Further information
-------------------

Tested projects are mostly cmake based and worked prior update 2.
Comment 1 Vladimir Kvashin 2014-06-30 14:10:21 UTC
As I understand that's code model a repository issue - what was got from there appeared to be an instance of IncludeImpl instead of FileImpl. So the code model repository is broken for unknown reason.

As a workaround, please remove ${nb_userdir}/var/cache/cnd/model
Comment 2 -eki 2014-06-30 15:07:32 UTC
I guess the path is "/home/<username>/.cache/netbeans/8.0/cnd/model" on linux. 

After deleting this folder the problems mentioned above are gone - thank you!

I'll check this on another machine too and report back.
Comment 3 -eki 2014-06-30 16:06:43 UTC
Seems solved.

ps. is it up on me to close this bug or should devs do this?
Comment 4 Vladimir Kvashin 2014-06-30 16:31:17 UTC
Thank you for info. We'll close it after we make some additional checks.