Bug 272621 - gcc's #include_next is not interpreted
Summary: gcc's #include_next is not interpreted
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: git master
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-06 14:20 UTC by Przemek
Modified: 2016-09-08 20:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Przemek 2011-05-06 14:20:27 UTC
Version:           git master (using Devel) 
OS:                Linux

If project tree uses include files with #include_next, some symbols are not resolved (as they are not loaded).
One of examples is /usr/include/limits.h. Architecture dependent limits.h files are not included and not parsed.

Reproducible: Always

Steps to Reproduce:
use eg. PATH_MAX in simple program.

Actual Results:  
symbol PATH_MAX is *not* resolved

Expected Results:  
symbol PATH_MAX *is* resolved

kde 4.6 from FACTORY repo.
Comment 1 Kevin Funk 2016-09-08 20:19:56 UTC
Hello!

We are working on a new clang-based C/C++ language plugin for KDevelop 5 which
supersedes the old C++ plugin in KDevelop 4. See e.g.:
https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available

Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather
want to supply a good Clang based C++ experience for KDevelop 5 than wasting
our time on the legacy C++ support for KDevelop 4.

With the new clang-based C/C++ language plugin, the bug presented here does not
occur. In my testing. For these reasons, I'll close this bug. Please stay tuned
for KDevelop 5.

If you think this bug is applicable to Clang/KDevelop 5, please reopen the
report and add new information on how to reproduce the bug there.