[kdevelop] [Bug 405221] Faulty code parsing with Clang backend

2019-09-19 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=405221

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.4.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 405221] Faulty code parsing with Clang backend

2019-09-19 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=405221

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||kdevelop/commit/c315333c4aa
   ||38ec9d05f101844fc4729717fd1
   ||3b
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Milian Wolff  ---
Git commit c315333c4aa38ec9d05f101844fc4729717fd13b by Milian Wolff, on behalf
of Axel Kellerman.
Committed on 20/09/2019 at 04:06.
Pushed by mwolff into branch '5.4'.

gcclikecompiler: properly resolve include paths with symbolic links

Make sure include paths containing symbolic links are canonicalized
- and thereby properly resolved - before wrapping them in a Path
object. This is necessary, as class Path is not properly handling
symbolic links.

M  +1-1   
plugins/custom-definesandincludes/compilerprovider/gcclikecompiler.cpp

https://invent.kde.org/kde/kdevelop/commit/c315333c4aa38ec9d05f101844fc4729717fd13b

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 405221] Faulty code parsing with Clang backend

2019-09-05 Thread Axel Kellermann
https://bugs.kde.org/show_bug.cgi?id=405221

Axel Kellermann  changed:

   What|Removed |Added

 CC||axel.kellerm...@gmx.de

--- Comment #2 from Axel Kellermann  ---
See https://phabricator.kde.org/D23303

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 405221] Faulty code parsing with Clang backend

2019-04-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405221

--- Comment #1 from axel_kellerm...@mentor.com ---
Just wanted to keep you posted. The culprit turned out to be an old, leftover,
auto-generated sddm.conf file that contained the line

DefaultPath=/bin:/usr/bin:/usr/local/bin

This made /bin the first element of PATH in all my user sessions and led to the
faulty behavior as described above.
With the new sddm.conf default

DefaultPath=/usr/local/sbin:/usr/local/bin:/usr/bin

the problem no longer occurs.

But maybe we should apply the proposed patch anyway to make include path
enumeration more robust?

-- 
You are receiving this mail because:
You are watching all bug changes.