[kdevelop] [Bug 369374] Background parser slows down the GUI thread for large projects

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369374

--- Comment #1 from Milian Wolff  ---
The short living threads are used by libclang for crash resilience. You can
verify whether that really is the problem by temporarily disabling that
feature. For that, you will need to recompile KDevelop though, and add a call
to `clang_toggleCrashRecovery(false)`, e.g. in
`kdevelop/language/clang/duchain/clangindex.cpp`, before the call to
`clang_CXIndex_setGlobalOptions`.

That said, I doubt that this is the reason for the high CPU usage. Could you
please use a profiler to get some hard data?

- install debug symbols for kdevelop + kdevplatform
- profile CPU with perf:

perf record --call-graph dwarf --pid $(pidof kdevelop)
# wait a couple of seconds while kdevelop has high CPU usage
# ^C -> this stops the record and writes a `perf.data` file

then run

perf report --no-children -g graph | bzip2 > perf.report.bz2

and upload the report here.

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

[valgrind] [Bug 327881] False Positive Warning on std::atomic_bool

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=327881

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Milian Wolff  ---
I can confirm this behavior, seems like the suppression files must be extended
to ignore anything happening within std::atomic* ?

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

[kdevelop] [Bug 369168] New: Clang Child Diagnostics can contain relative paths

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369168

Bug ID: 369168
   Summary: Clang Child Diagnostics can contain relative paths
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

Application: kdevelop (5.0.1)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.2-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
I looked at an error in a template triggered by some other file that included a
header and tried to instantiate it incorrectly.

Clang created child diagnostics that referred to some files in the child
diagnostics with relative paths. Clicking on them in the problem view triggers
assertions.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7febd9341840 (LWP 29285))]

Thread 15 (Thread 0x7feb24fab700 (LWP 31639)):
#0  0x7febc845010f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7febc9c29ac4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7febc9c29b09 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7feb27fff700 (LWP 29369)):
#0  0x7febd19324ed in read () from /usr/lib/libc.so.6
#1  0x7febc5eaebc0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7febc5e6bb36 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7febc5e6c004 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7febc5e6c17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7febd277359b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7febd271d0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7febd25400f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7febcfb45a64 in KDevelop::CompletionWorkerThread::run
(this=0x45c9c20) at
/home/milian/projects/kf5/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#9  0x7febd2544d78 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7feb62ffe700 (LWP 29330)):
#0  0x7febc5e6b553 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7febc5e6bf8b in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7febc5e6c17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7febd277359b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7febd271d0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7febd25400f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7febd2544d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7feb7a868700 (LWP 29320)):
#0  0x7febc845010f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7febd2545c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7febce6157be in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=0x1db90c0, th=0x7feb74003450) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:594
#3  0x7febce6153d8 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=, th=0x80, threadWasBusy=, suspendIfInactive=, justReturning=) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:554
#4  0x7febce61a2c0 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1db9210, th=0x7feb74003450, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:66
#5  0x7febce61a4d0 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:61
#6  0x7febce61596e in ThreadWeaver::Weaver::applyForWork (this=, th=0x35e1, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7febce61a3ff in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1db9210, th=0x7feb74003450, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7febce61a4d0 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, 

[kdevelop] [Bug 369168] Clang Child Diagnostics can contain relative paths [ASSERT: "!inputUrl.isRelative()"]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369168

Milian Wolff  changed:

   What|Removed |Added

   Priority|NOR |VHI
Summary|Clang Child Diagnostics can |Clang Child Diagnostics can
   |contain relative paths  |contain relative paths
   ||[ASSERT:
   ||"!inputUrl.isRelative()"]
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[kdevplatform] [Bug 355100] deadlock in backgroundparser [mutex locked while plugin gets loaded]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355100

Milian Wolff  changed:

   What|Removed |Added

 CC||afie...@gmail.com

--- Comment #8 from Milian Wolff  ---
*** Bug 368375 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 368375] KDevelop hangs while parsing project

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368375

Milian Wolff  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #3 from Milian Wolff  ---


*** This bug has been marked as a duplicate of bug 355100 ***

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

[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368568

--- Comment #4 from Milian Wolff  ---
The crash clearly points towards QQmlApplicationEngine which has zero to do
with the patch review code and no I cannot reproduce this.

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

[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368689

--- Comment #6 from Milian Wolff  ---
Can you please be exact in what you mean with "try editing"? What exactly are
you doing? Inserting text (if so, which one, where?) Or are you removing
something? Again, what - where?

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

[kdevelop] [Bug 368826] KDevelop crashed when trying to open a CMake project

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368826

--- Comment #1 from Milian Wolff  ---
potentially related to bug 331227.

@op: can you please reproduce the crashe while running kdevelop through
valgrind?

valgrind --smc-check=all-non-file --track-origins=yes kdevelop -s ...

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

--- Comment #4 from Milian Wolff  ---
Oh, and you could also try out heaptrack with the project you can reproduce the
issue with:


heaptrack kdevelop -s ...
# wait a few seconds while verifying that the process is actually exhibiting
the bad behavior
# ctrl + C to quit, alternatively use `ulimit -v` to set some limit on the
virtual memory to prevent
# it from taking down your other applications

then send us the heaptrack.gz data file, e.g. upload it here

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

--- Comment #3 from Milian Wolff  ---
I cannot reproduce this with the attached file. Can you try to create a MWE
with a tarball of a project I can open in KDevelop?

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

[kdevelop] [Bug 369036] KDevelop crashes on quit [TopDUContextDynamicData::loadData failed to find file]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369036

Milian Wolff  changed:

   What|Removed |Added

Summary|KDevelop crashes on quit|KDevelop crashes on quit
   ||[TopDUContextDynamicData::l
   ||oadData failed to find
   ||file]
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
   Priority|NOR |VHI

--- Comment #1 from Milian Wolff  ---
It failed to open the cached file. This really must be cleaned up - I don't
like us crashing/asserting when trying to load data from the cache.
Additionally, I'd like to find a way to not _load_ data on shutdown. Finally, I
wonder whether top contexts need to clean their item index at all...

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

[kdevelop] [Bug 368855] changing files via git (rebase, checkout) causes 100% CPU usage on 2 cores

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368855

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #4 from Milian Wolff  ---
not a backtrace, a profile is needed. Please get one when you see 100% CPU
usage via:

perf record --call-graph dwarf --pid $(pidof kdevelop)
# wait a couple of seconds
^C

then create a report file and upload it here:

perf report --no-children -g graph --stdio | bzip2 > perf.report.bz2

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

[kdevelop] [Bug 361716] Duplicate suggestions in include file completion

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361716

--- Comment #5 from Milian Wolff  ---
Heh, I should pay more attention to the surroundings of the actual bug ;-)

Sadly, I cannot reproduce this locally. Any chance you could add some debug
output and debug it locally to see why it adds two files for you?

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

[kdevelop] [Bug 368695] Crash when using QuickOpen

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368695

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/5da01380d6223d2e63
   ||00cba1da29e6f031055107
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Milian Wolff  ---
Git commit 5da01380d6223d2e6300cba1da29e6f031055107 by Milian Wolff.
Committed on 13/09/2016 at 21:12.
Pushed by mwolff into branch '5.0'.

Don't ever return empty icon names, return "none" instead as fallback.

M  +3-0project/projectmodel.cpp

http://commits.kde.org/kdevplatform/5da01380d6223d2e6300cba1da29e6f031055107

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

[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368568

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Milian Wolff  ---
crashes deep inside Qt, please report upstream

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

[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368689

--- Comment #2 from Milian Wolff  ---
can you please give us an example project (i.e. something we can test
ourselves) and tell us which file you are editing, how, and where, to reproduce
the issue?

this is a really important thing to get fixed, but so far we did not find a
reliable way to trigger the issue, thus making the bug fixing pretty much
impossible at this point

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

[kdevelop] [Bug 368460] function signature picks up template parameter names

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368460

--- Comment #4 from Milian Wolff  ---
I think https://reviews.llvm.org/D13599 can help to get this fixed. In the
meantime, ideas on how to improve that situation are welcome :)

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

[kdevelop] [Bug 368318] Crash during session restore at startup

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368318

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #4 from Milian Wolff  ---
Ah, the issue here is 

kdevelop(21625)/default unknown: Failed to load item with identity 111

That belongs to the QML/JS plugin (QmlJSNormalDUContext)- did you
uninstall/disable that one?

I still think we should handle such cases better, somehow...

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

[frameworks-ktexteditor] [Bug 368477] Shortcut key to navigate the code completion dialog

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368477

Milian Wolff  changed:

   What|Removed |Added

Version|5.0.0   |unspecified
   Keywords||junior-jobs
 Ever confirmed|0   |1
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
Product|kdevelop|frameworks-ktexteditor
 Status|UNCONFIRMED |CONFIRMED
  Component|general |general

--- Comment #1 from Milian Wolff  ---
yep, sounds like a good idea but must be implemented in ktexteditor

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

[kdevelop] [Bug 361716] Duplicate suggestions in include file completion

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361716

Milian Wolff  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #3 from Milian Wolff  ---
Alexander, any chance we can reproduce this with a project that is accessible
to us? Do you also see this in KDE projects by any chance e.g.? Or any other
FOSS project we can test ourselves?

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

[kdevelop] [Bug 339658] [OS X] debuggin: controlling gdb

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339658

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Milian Wolff  ---
ok, closing the gdb stuff as unmaintained then on os x

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

[kdevelop] [Bug 340564] crash when opening an empty file

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340564

Milian Wolff  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

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

[kdevelop] [Bug 368458] Can't change highlight color used when hovering identifier

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368458

--- Comment #3 from Milian Wolff  ---
I think the proper way to implement that would be to add a plugin hook into the
ktexteditor fonts config page, then add our stuff there into a custom
group. this would also allow us to add configurations for the other syntax
highlighting colors

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

[kdevelop] [Bug 368460] function signature picks up template parameter names

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368460

--- Comment #2 from Milian Wolff  ---
Git commit 0dac419e2fe7428ed9ce6134c1ff674874ccca2a by Milian Wolff.
Committed on 08/09/2016 at 17:01.
Pushed by mwolff into branch '5.0'.

Add unit test with expected failure for template functions with args.

Since we put template parameters into the function context, which
usually starts with the function arguments, things get confused
elsewhere. We really need to create a separate context for the
template parameters...

M  +34   -0languages/clang/tests/test_duchain.cpp
M  +1-0languages/clang/tests/test_duchain.h

http://commits.kde.org/kdevelop/0dac419e2fe7428ed9ce6134c1ff674874ccca2a

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

[kdevelop] [Bug 368458] Can't change highlight color used when hovering identifier

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368458

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Milian Wolff  ---
true

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

[kdevelop] [Bug 368460] function signature picks up template parameter names

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368460

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Milian Wolff  ---
the problem is that we don't open another context for the template paramters,
and simply put their declarations into the function context, which usually
starts with the function arguments... this then confuses
DUChainUtils::getArgumentContext which then leads to wrong association in
AbstractDeclarationNavigationContext::htmlFunction (and probably elsewhere).

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

[kdevelop] [Bug 348636] Failure to recognize C++ template-style variable declaration

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348636

Milian Wolff  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

NOTE: I did not actually test this, because you did not provide a MWE. I am
pretty sure clang parses it correctly though, and so will we then.

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

[kdevelop] [Bug 368460] New: function signature picks up template parameter names

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368460

Bug ID: 368460
   Summary: function signature picks up template parameter names
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

seems like we use the wrong clang api somewhere, or it's unclear

Reproducible: Always

Steps to Reproduce:
struct Foo {};
template
T *acquire(const Foo ) { return new T; }

hover over acquire and look at whats getting shown:

Actual Results:  
T* acquire(const Foo );

Expected Results:  
T* acquire(const Foo );

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

[kdevelop] [Bug 360567] Wrong parameter info displayed for variadic function templates

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360567

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Milian Wolff  ---
In code completion, I see `void print(Args&&...)` being displayed, which seems
to be correct. Where do you request code completion to see `void print()`
instead? As explained by Matt, showing only the two available options sounds
wrong to me.

Kevin, I'll report a new bug for your issue and look into that now.

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

[kdevelop] [Bug 338348] failed to parse template parameter of a template

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=338348

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.0.0

--- Comment #5 from Milian Wolff  ---
just checked again, with kdev 5.0 I don't see any obvious issues here anymore,
you even get code completion.

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

[kdevelop] [Bug 334003] C++ parser takes class method template instantiation as method declaration

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=334003

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Milian Wolff  ---
can you please add a full example that I can copy'n'paste into my editor to
check whether this is still valid in the clang backend?

thanks!

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

[kdevelop] [Bug 333869] C++ parser does not accept *this as lvalue in template specialization

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333869

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.0.0

--- Comment #1 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

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

[kdevelop] [Bug 329347] type deduction fails for template member of template class when used from class member

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=329347

Milian Wolff  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Milian Wolff  ---
works with the new clang backend, but only once the parse error gets fixed:

template  class Bar
{
public:
  template< typename D > D* foo();
  T bar();
};

template< typename T >
T Bar::bar() // NOTE: you missed the  after Bar here
{
  auto i = foo< int >();

  Bar q;
  auto j = q.foo();
}

auto k = Bar().foo();

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

[kdevelop] [Bug 258459] implementing method of template class creates invalid code

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=258459

Milian Wolff  changed:

   What|Removed |Added

Summary|Code completion fails on|implementing method of
   |templates   |template class creates
   ||invalid  code

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

[kdevelop] [Bug 258459] Code completion fails on templates

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=258459

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
  Component|Language Support: CPP   |Language Support: CPP
   ||(Clang-based)
 Ever confirmed|0   |1

--- Comment #4 from Milian Wolff  ---
still valid in the clang backend, there we get:


template void Test::someFuction(T arg)
{
}

note the missing "typename" in the `template` part

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

[kdevelop] [Bug 220287] missing use reports for `this->member` in class templates

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=220287

--- Comment #8 from Milian Wolff  ---
output from the clang AST, the issue is the opaque dependent type, which also
bugs us elsewhere:

  CXXConstructor (24) | type: "void ()" (111) | display: "C()" | loc:
test.cpp@[(8,5),(15,6)] | sp-name-range: [(8,5),(8,6)] | isDecl
CompoundStmt (202) | loc: test.cpp@[(8,9),(15,6)] | sp-name-range:
[(0,0),(0,0)] 
  BinaryOperator (114) | type: "" (26) | loc:
test.cpp@[(10,9),(10,19)] | sp-name-range: [(10,9),(10,15)] 
MemberRefExpr (102) | type: "int" (17) | display: "A_test" | loc:
test.cpp@[(10,9),(10,15)] | sp-name-range: [(10,9),(10,15)] | isUse
IntegerLiteral (106) | type: "int" (17) | loc:
test.cpp@[(10,18),(10,19)] | sp-name-range: [(10,18),(10,19)] 
  BinaryOperator (114) | type: "" (26) | loc:
test.cpp@[(11,9),(11,20)] | sp-name-range: [(11,9),(11,15)] 
MemberRefExpr (102) | type: "int" (17) | display: "C_test" | loc:
test.cpp@[(11,9),(11,15)] | sp-name-range: [(11,9),(11,15)] | isUse
IntegerLiteral (106) | type: "int" (17) | loc:
test.cpp@[(11,18),(11,20)] | sp-name-range: [(11,18),(11,20)] 
  BinaryOperator (114) | type: "" (26) | loc:
test.cpp@[(13,9),(13,25)] | sp-name-range: [(13,9),(13,13)] 
MemberRefExpr (102) | type: "" (26) | loc:
test.cpp@[(13,9),(13,21)] | sp-name-range: [(13,9),(13,13)] 
  CXXThisExpr (132) | type: "C *" (101) | loc:
test.cpp@[(13,9),(13,13)] | sp-name-range: [(13,9),(13,13)] 
IntegerLiteral (106) | type: "int" (17) | loc:
test.cpp@[(13,24),(13,25)] | sp-name-range: [(13,24),(13,25)] 
  BinaryOperator (114) | type: "" (26) | loc:
test.cpp@[(14,9),(14,25)] | sp-name-range: [(14,9),(14,13)] 
MemberRefExpr (102) | type: "" (26) | loc:
test.cpp@[(14,9),(14,21)] | sp-name-range: [(14,9),(14,13)] 
  CXXThisExpr (132) | type: "C *" (101) | loc:
test.cpp@[(14,9),(14,13)] | sp-name-range: [(14,9),(14,13)] 
IntegerLiteral (106) | type: "int" (17) | loc:
test.cpp@[(14,24),(14,25)] | sp-name-range: [(14,24),(14,25)]

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

[kdevelop] [Bug 220287] missing use reports for `this->member` in class templates

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=220287

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
  Component|Language Support: CPP   |Language Support: CPP
   ||(Clang-based)
Summary|deriving from a template|missing use reports for
   |class causes kdevelop's c++ |`this->member` in class
   |analysis some trouble   |templates
 Status|UNCONFIRMED |CONFIRMED

--- Comment #7 from Milian Wolff  ---
most of this got fixed with the move to clang, but we seem to not get enough
information from clang for this example:
template
struct A {
int A_test;
};

template
struct C : A {
C() {
// uses get reported here
A_test = 2;
C_test = 42;
// but not here
this->A_test = 3;
this->C_test = 4;
}
int C_test;
};

struct B {
B() {
// this works fine
foo++;
this->foo--;
}
int foo;
};

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

[kdevelop] [Bug 294917] Parsing of default template arguments fails if they contain template parameters

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=294917

Milian Wolff  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

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

[kdevelop] [Bug 302061] KDevelop shows errors on variadic template argument expansion in "using" declarations

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=302061

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.0.0

--- Comment #1 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

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

[kdevelop] [Bug 305940] "Move into source" on templated class member does not generate template declaration in source

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=305940

Milian Wolff  changed:

   What|Removed |Added

Version|4.3.1   |git master
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
  Component|Language Support: CPP   |Language Support: CPP
   ||(Clang-based)

--- Comment #1 from Milian Wolff  ---
still valid in the clang backend in kdev 5

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

[kdevelop] [Bug 309073] forward declare template in a namespace, then closing the namespace and reopening it again to specialize the template makes kdevelop fail to find that specialization

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=309073

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.0.0

--- Comment #2 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

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

[kdevelop] [Bug 312552] KDevelop fails to find struct specializations when the template is in a different header

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=312552

Milian Wolff  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Milian Wolff  ---
fixed in kdevelop 5 with the new clang backend

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

[kdevplatform] [Bug 326877] The "Show uses" and "Find uses" feature fails to recognize templated methods.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=326877

Milian Wolff  changed:

   What|Removed |Added

   Version Fixed In||5.0.0

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

[kdevplatform] [Bug 326877] The "Show uses" and "Find uses" feature fails to recognize templated methods.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=326877

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Milian Wolff  ---
this works fine in KDevelop 5 with the new clang backend in my test

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

[kdevplatform] [Bug 314059] Automatic area switching does not restore correct editor

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=314059

Milian Wolff  changed:

   What|Removed |Added

  Component|shell   |debugger
   Severity|major   |normal
 CC||niko.s...@gmail.com

--- Comment #1 from Milian Wolff  ---
when switching to the debug area, we show the wrong file first, but when
switching back everything gets properly restored for me. since we focus the
right doc when we hit a breakpoint, I'm decreasing the importance of this bug

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

[kdevelop] [Bug 293750] when creating cmake test

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=293750

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Milian Wolff  ---
We completely removed the old cmake parsing logic for KDevelop 5 and will work
on integrating the cmake server in the future (see e.g.
http://cppcast.com/2016/08/stephen-kelly/ or
https://steveire.wordpress.com/2016/01/24/cmake-daemon-for-user-tools/). This
bug only applies to KDevelop 4, but we don't have to resources to maintain it
and instead push our effort into KDev 5. I hope you understand that I'm thus
closing this report.

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

[kdevelop] [Bug 339658] [OS X] debuggin: controlling gdb

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339658

Milian Wolff  changed:

   What|Removed |Added

   Severity|major   |normal

--- Comment #4 from Milian Wolff  ---
decreasing importance, OS X is simply not supported yet

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

[kdevelop] [Bug 239004] Custom Makefile Project has wrong working directory

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=239004

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/d28d5179632b42238f
   ||c0ac9a2d667082756f39e4
 Resolution|--- |FIXED

--- Comment #6 from Milian Wolff  ---
Git commit d28d5179632b42238fc0ac9a2d667082756f39e4 by Milian Wolff.
Committed on 07/09/2016 at 21:40.
Pushed by mwolff into branch '5.0'.

Update PWD env var when setting working directory on execute jobs.

We actually properly set the working directory, but when scripts
rely on the PWD env var, and we don't update that, things can break.
This patch simply updates the PWD env var if set before to the new
working directory before running the job.

M  +8-3outputview/outputexecutejob.cpp

http://commits.kde.org/kdevplatform/d28d5179632b42238fc0ac9a2d667082756f39e4

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

[kdevelop] [Bug 239004] Custom Makefile Project has wrong working directory

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=239004

--- Comment #5 from Milian Wolff  ---
still valid in 5.0, looking into it now

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

[kdevplatform] [Bug 313206] add copy + select feature to use report

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=313206

Milian Wolff  changed:

   What|Removed |Added

   Severity|major   |wishlist
Summary|can only click on "Line xy" |add copy + select feature
   |but not the complete line   |to use report

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

[kdevelop] [Bug 361958] select + copy text actions for uses report

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #1 from Milian Wolff  ---
wtf, bugzilla clearly edited the wrong bug report here... what was the old
title of this report?

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

[kdevelop] [Bug 340843] kdevpatchreview stuck in infinite loop

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340843

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
   Severity|major   |crash
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Milian Wolff  ---
Hey Joris,

sorry for the long delay. Can you show us how to reproduce this with an open
source project, i.e. when you clone something from github, what steps do you do
to trigger this issue? I haven't seen it myself.

pasting backtrace inline for searchability:

gdb /usr/bin/kdevelop 2258
GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kdevelop...Reading symbols from
/usr/lib/debug//usr/bin/kdevelop...done.
done.
Attaching to program: /usr/bin/kdevelop, process 2258
Reading symbols from /usr/lib/libkdecore.so.5...Reading symbols from
/usr/lib/debug//usr/lib/libkdecore.so.5.14.1...done.
done.
Loaded symbols for /usr/lib/libkdecore.so.5
Reading symbols from /usr/lib/libkdevplatforminterfaces.so.8...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/libkdevplatforminterfaces.so.8
Reading symbols from /usr/lib/libkdevplatformshell.so.8...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libkdevplatformshell.so.8
Reading symbols from /usr/lib/libktexteditor.so.4...Reading symbols from
/usr/lib/debug//usr/lib/libktexteditor.so.4.14.1...done.
done.
Loaded symbols for /usr/lib/libktexteditor.so.4
Reading symbols from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4...Reading
symbols from
/usr/lib/debug/.build-id/67/33368b48c5db56d1b1bf503a85bbeb3b3603df.debug...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
Reading symbols from /usr/lib/libkdeclarative.so.5...Reading symbols from
/usr/lib/debug//usr/lib/libkdeclarative.so.5.14.1...done.
done.
Loaded symbols for /usr/lib/libkdeclarative.so.5
Reading symbols from /usr/lib/libsublime.so.8...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libsublime.so.8
Reading symbols from /usr/lib/libkdeui.so.5...Reading symbols from
/usr/lib/debug//usr/lib/libkdeui.so.5.14.1...done.
done.
Loaded symbols for /usr/lib/libkdeui.so.5
Reading symbols from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4...Reading symbols
from
/usr/lib/debug/.build-id/18/1229821adfedcdd42c5e451261bbb57fc858c7.debug...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
Reading symbols from /usr/lib/x86_64-linux-gnu/libQtGui.so.4...Reading symbols
from
/usr/lib/debug/.build-id/aa/27439fd194a575950e56ea36adee96c11a852d.debug...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Reading symbols from /usr/lib/x86_64-linux-gnu/libQtCore.so.4...Reading symbols
from
/usr/lib/debug/.build-id/5e/1a0285d6788a1593298747246ecff63ff2b81e.debug...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from
/usr/lib/debug//lib/x86_64-linux-gnu/libc-2.19.so...done.
done.
Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4...Reading
symbols from
/usr/lib/debug/.build-id/d3/be07c8afc2b6b095a95abce5701c15b93c1d6a.debug...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4
Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1
Reading symbols from /lib/x86_64-linux-gnu/libbz2.so.1.0...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libbz2.so.1.0
Reading symbols from /lib/x86_64-linux-gnu/liblzma.so.5...(no debugging symbols
found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/liblzma.so.5
Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...Reading symbols
from /usr/lib/debug//lib/x86_64-linux-gnu/libpthread-2.19.so...done.
done.
[New LWP 2608]
[New LWP 2607]
[New LWP 2442]
[New LWP 2433]
[New LWP 2321]
[New 

[kdevelop] [Bug 361958] select + copy text actions for uses report

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

Milian Wolff  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[kdevelop] [Bug 361958] select + copy text actions for uses report

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

Milian Wolff  changed:

   What|Removed |Added

   Severity|major   |normal
 Status|UNCONFIRMED |CONFIRMED
Summary|outline dropdown widget |select + copy text actions
   |jumps to function   |for uses report
   |implementation in another   |
   |file|
 Ever confirmed|0   |1

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

[kdevelop] [Bug 327168] Background parser hangs on specific code

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=327168

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Milian Wolff  ---
Hello!

We worked 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
https://www.kdevelop.org/news/kdevelop-500-released

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 try out
KDevelop 5, either by downloading it through your distro, or by playing around
with the AppImage:.

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.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers

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

[kdevplatform] [Bug 313206] can only click on "Line xy" but not the complete line

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=313206

--- Comment #4 from Milian Wolff  ---
Git commit 54113eb4ed975e682cf98fbcee5dffd5f43e250e by Milian Wolff.
Committed on 07/09/2016 at 21:11.
Pushed by mwolff into branch '5.0'.

Navigate to use when clicking anywhere in a use report line

The code for the use report is incredibly ugly and really needs
to be cleaned up. We could probably get away with generating a
single HTML report and use that for all matches, instead of
generating one widget (with two labels) per use, each with its
own HTML inside...

Doing it all in one document would also allow us to easily implement
a select + copy action.

M  +16   -8language/duchain/navigation/useswidget.cpp
M  +2-3language/duchain/navigation/useswidget.h

http://commits.kde.org/kdevplatform/54113eb4ed975e682cf98fbcee5dffd5f43e250e

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

[kdevelop] [Bug 368301] Error when launching an executable when "Environment Variables" are configured

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368301

Milian Wolff  changed:

   What|Removed |Added

   Severity|major   |crash

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

[kdevelop] [Bug 368292] Segfault when using gdb

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368292

Milian Wolff  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kdevplatform] [Bug 313206] can only click on "Line xy" but not the complete line

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=313206

--- Comment #3 from Milian Wolff  ---
still valid, would be nice to see this improved. the styling should ideally
stay the same, just with the capability to click on the whole line. I'll try
and see if I can fix that with a bit of CSS.

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

[kdevelop] [Bug 347388] KDevelop/KF5 Crash when expanding Classes -> All projects classes view

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347388

Milian Wolff  changed:

   What|Removed |Added

 Status|REOPENED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Milian Wolff  ---
I think this is an upstream bug and will need to be fixed there. alternatively,
it could be something messed up with the model. Yeah I think it would be
valuable to put the model under modeltest and ensure it passes those tests.
could you try that quickly? If it does not show anything, then we need to fix
it upstream by adding a safeguard there

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

[kdevelop] [Bug 359067] Auto-completion of method definitions does not follow declaration format or symbols, and breaks convention, and may also break compilation on some systems.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359067

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.0.0

--- Comment #3 from Milian Wolff  ---
in kdev 5 with our clang backend, the namespace issues does not arise, even
when using libstdc++. I'll report a wishrequest for the placement of const now

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

[kdevelop] [Bug 368422] source formatters should allow configuration of `const` placement, use it in code completion/implementation helpers

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368422

Milian Wolff  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kdevelop] [Bug 368422] New: source formatters should allow configuration of `const` placement, use it in code completion/implementation helpers

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368422

Bug ID: 368422
   Summary: source formatters should allow configuration of
`const` placement, use it in code
completion/implementation helpers
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

from bug 359067

Reproducible: Always

Steps to Reproduce:
#include 

class someClass
{
std::string const & getFoo();
};

use implement function

Actual Results:  

const std::string & someClass::getFoo()
{
}


Expected Results:  

std::string const & someClass::getFoo()
{
}

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

[kdevelop] [Bug 361390] Definition creator tries to override virtual methods

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361390

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Milian Wolff  ---
this got fixed in the meantime now, no? (by you, even?)

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

[kdevelop] [Bug 358205] crash in clang_Cursor_getParsedComment

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358205

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #5 from Milian Wolff  ---
this must be fixed upstream, and we need a reproducible way to trigger this. if
you have one that takes down kdevelop, please show it here and I'll create a
test out of it for upstream

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

[kdevelop] [Bug 367735] Problem in semantic analysis - cannot rename all variables after click in usage this variable

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367735

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Milian Wolff  ---
this should be enough to reproduce:

void foo()
{
int bar = 0;
bar++;
bar++;
bar++;
}

I agree that rename should be done everywhere.
Also, making it simpler to apply the change everywhere after doing the rename
would be nice to have.

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

[kdevelop] [Bug 368067] Wrong declaration is caught when class name as template parameter

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368067

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/a453eec244cd056aa9dc55
   ||162eb0b5c8a69d0d12
 Resolution|--- |FIXED

--- Comment #3 from Milian Wolff  ---
Git commit a453eec244cd056aa9dc55162eb0b5c8a69d0d12 by Milian Wolff.
Committed on 07/09/2016 at 12:59.
Pushed by mwolff into branch '5.0'.

Always open a context for class templates, i.e. also for declarations.

Forward declarations of class templates leaked their template paramter
declarations into the surrounding context, leading to potentially
wrong associations when looking for declarations based on their
identifier.

M  +5-1languages/clang/duchain/builder.cpp
M  +23   -0languages/clang/tests/test_duchain.cpp
M  +1-0languages/clang/tests/test_duchain.h

http://commits.kde.org/kdevelop/a453eec244cd056aa9dc55162eb0b5c8a69d0d12

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

[kdevelop] [Bug 368067] Wrong declaration is caught when class name as template parameter

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368067

--- Comment #2 from Milian Wolff  ---
We put the declarations of the template type parameters into the parent
context, which confuses our lookup. The solution would be to wrap those into
their own context, and then import that one into the ClassTemplate context. Or
maybe put them directly into the class template.

clang gives us:

AST tree successfully generated
ClassDecl (4) | type: "Foo" (105) | display: "Foo" | loc:
tests/files/bug367893.cpp@[(1,1),(1,10)] | sp-name-range: [(1,7),(1,10)] |
isDecl
ClassTemplate (31) | display: "Bar" | loc:
tests/files/bug367893.cpp@[(2,1),(2,33)] | sp-name-range: [(2,30),(2,33)] |
isDecl
  TemplateTypeParameter (27) | type: "Foo" (1) | canonical type:
"type-parameter-0-0" (1) | display: "Foo" | loc:
tests/files/bug367893.cpp@[(2,10),(2,22)] | sp-name-range: [(2,19),(2,22)] |
isDecl
ClassDecl (4) | type: "Foo" (105) | display: "Foo" | loc:
tests/files/bug367893.cpp@[(4,1),(4,26)] | sp-name-range: [(4,7),(4,10)] |
isDecl
  CXXMethod (21) | type: "void ()" (111) | display: "foo()" | loc:
tests/files/bug367893.cpp@[(4,13),(4,23)] | sp-name-range: [(4,18),(4,21)] |
isDecl
CXXMethod (21) | type: "void ()" (111) | display: "foo()" | loc:
tests/files/bug367893.cpp@[(6,1),(6,21)] | sp-name-range: [(6,11),(6,14)] |
isDecl
  TypeRef (43) | type: "Foo" (105) | display: "class Foo" | loc:
tests/files/bug367893.cpp@[(6,6),(6,9)] | sp-name-range: [(6,6),(6,9)] | isUse
  CompoundStmt (202) | loc: tests/files/bug367893.cpp@[(6,17),(6,21)] |
sp-name-range: [(0,0),(0,0)] 
no problems encountered during parsing

we build:

  Top-Context "Global" (owner:  0x0 ) 0x7f3fcc004460 "" [ "" ] [ (0, 0)  -> 
(2147483647, 2147483647) ] "/tmp/testfile_Bh5300.cpp" 
 Declaration: "Foo" [ "Foo" ] 0x7f3fcc04a400 (internal ctx: 0x0 ) [ (1, 14)
 ->  (1, 17) ] , no definition,  1 use(s). 
   File: "/tmp/testfile_Bh5300.cpp" 
 Use: [ (6, 13)  ->  (6, 16) ] 
 Declaration: "Foo Foo" [ "Foo" ] 0x7f3fcc086f60 (internal ctx: 0x0 ) [ (2,
26)  ->  (2, 29) ] , no definition,  1 use(s). 
   File: "/tmp/testfile_Bh5300.cpp" 
 Use: [ (6, 13)  ->  (6, 16) ] 
 Declaration: "Bar" [ "Bar" ] 0x7f3fcc086e40 (internal ctx: 0x0 ) [ (2, 37)
 ->  (2, 40) ] , no definition,  0 use(s). 
 Declaration: "class Foo" [ "Foo" ] 0x7f3fcc0873a0 (internal ctx:
0x7f3fcc072cb0 ) [ (4, 14)  ->  (4, 17) ] , defined,  1 use(s). 
   File: "/tmp/testfile_Bh5300.cpp" 
 Use: [ (6, 13)  ->  (6, 16) ] 
Context "Class" (owner:  0x7f3fcc0873a0 ) 0x7f3fcc072cb0 "Foo" [ "Foo" ] [
(4, 8)  ->  (4, 33) ] "" 
   1 Declarations, 1 child-contexts 
  Context "Function" (owner:  0x7f3fcc087e90 ) 0x7f3fcc086e10 "foo" [
"Foo::foo" ] [ (4, 20)  ->  (4, 30) ] "" 
 0 Declarations, 0 child-contexts 
Context "Helper" (owner:  0x0 ) 0x7f3fcc087010 "Foo" [ "Foo" ] [ (6, 8)  ->
 (6, 28) ] "" 
   1 Declarations, 1 child-contexts 
  Context "Function" (owner:  0x7f3fcc0879c0 ) 0x7f3fcc087a00 "foo" [
"Foo::foo" ] [ (6, 8)  ->  (6, 28) ] "" 
 0 Declarations, 1 child-contexts 
Context "Other" (owner:  0x0 ) 0x7f3fcc0a2170 "" [ "Foo::foo" ] [ (6,
24)  ->  (6, 28) ] "" 
   0 Declarations, 0 child-contexts

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Milian Wolff  ---
 "stutter" and backtrace looks like you ran out of memory, leading to swapping
and eventually OOM probably. could that be the case?

what project are you trying to load - can we try to reproduce and see how it
performs for us? maybe it's exhibiting some bad behavior somewhere in our code
and we could optimize that. but with just this backtrace, there's not much we
can do, I'm afraid to say

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

[kdevelop] [Bug 367898] kdevelop crashed while editing documents

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367898

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Milian Wolff  ---
Hm, crash inside libclang, must be fixed upstream... If you have sources that
trigger this reproducibly, please report that upstream at

https://llvm.org/bugs/show_bug.cgi?id=24280

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

[kdevelop] [Bug 368097] Kdevelop5 contains GPL-3.0 files

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368097

--- Comment #1 from Milian Wolff  ---
This is inside a plugin. Would it be enough to make the plugin GPL 3?

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

[kdevelop] [Bug 367837] KDevelop crashes when trying to debug from command-line

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367837

--- Comment #7 from Milian Wolff  ---
actually, just commit it right away if you have the rights to do so. it looks
good to me

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

[kio] [Bug 368278] ksmserver crash takes down KDevelop while destroying Q_QGS_s_pKDirWatchSelf

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368278

Milian Wolff  changed:

   What|Removed |Added

Summary|Crash when starting |ksmserver crash takes down
   |project's Build operation   |KDevelop while destroying
   |while Install was in|Q_QGS_s_pKDirWatchSelf
   |progress|

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

[kdevplatform] [Bug 355100] deadlock in backgroundparser [mutex locked while plugin gets loaded]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355100

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/8c46e8e765857b9e4d
   ||09b78c6896100dc150f964
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Milian Wolff  ---
Git commit 8c46e8e765857b9e4d09b78c6896100dc150f964 by Milian Wolff.
Committed on 06/09/2016 at 20:17.
Pushed by mwolff into branch '5.0'.

Release the background parser lock while creating parse jobs.

This fixes a deadlock due to lock order inversion. We often elsewhere
access the background parser while holding the DUChain lock. Here,
we used to lock the background parser and then potentially locked the
DUChain. This was desastrous.

The patch here now unlocks the background parser while creating the
parse job, and relocks it again to insert the job into its internal
data structurs.

Because the background parser only ever creats jobs from the main
thread, and only one at most, this is safe to do.

M  +16   -1language/backgroundparser/backgroundparser.cpp
M  +0-4language/backgroundparser/tests/test_backgroundparser.cpp

http://commits.kde.org/kdevplatform/8c46e8e765857b9e4d09b78c6896100dc150f964

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

[kdevelop] [Bug 368318] Crash during session restore at startup

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368318

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Milian Wolff  ---
Did it crash before that? Looks like the DUChain info got messed up and then
triggered a crash further down the road :(

not much we can do about this if you cannot reproduce it, I fear. Except
rewriting the whole serialization to introduce more safeguards, like
checksumming and stuff

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

[kdevplatform] [Bug 368322] Job not fully stopped when starting non-existing debugger executable

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368322

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Milian Wolff  ---
saw this today as well

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

[kdevelop] [Bug 365635] signature assistant unusable since assistant-ng merge

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365635

--- Comment #2 from Milian Wolff  ---
Git commit df1ddcced45e56ade604c25fff45bf8b3a35dfb1 by Milian Wolff.
Committed on 06/09/2016 at 12:53.
Pushed by mwolff into branch '5.0'.

Disable expected failures when we run against Clang 3.9

The issues got fixed upstream by ogoffart, thanks!

M  +4-0languages/clang/tests/test_assistants.cpp

http://commits.kde.org/kdevelop/df1ddcced45e56ade604c25fff45bf8b3a35dfb1

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

[kdevplatform] [Bug 355100] deadlock in backgroundparser [mutex locked while plugin gets loaded]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355100

--- Comment #6 from Milian Wolff  ---
Git commit 64f72d3fad28261f97cff6837526d69f6bb72837 by Milian Wolff.
Committed on 06/09/2016 at 11:16.
Pushed by mwolff into branch '5.0'.

Add test to trigger deadlock in BackgroundParser.

To run it, use:

$ TEST_BUG_355100=1 ./test_backgroundparser testNoDeadlockInJobCreation

Otherwise, we'll skip the deadlock to prevent issues on the CI.

M  +66   -4language/backgroundparser/tests/test_backgroundparser.cpp
M  +3-0language/backgroundparser/tests/test_backgroundparser.h
M  +5-1language/backgroundparser/tests/testlanguagesupport.cpp
M  +1-0language/backgroundparser/tests/testlanguagesupport.h
M  +5-1language/backgroundparser/tests/testparsejob.cpp
M  +3-0language/backgroundparser/tests/testparsejob.h

http://commits.kde.org/kdevplatform/64f72d3fad28261f97cff6837526d69f6bb72837

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

[kdevelop] [Bug 358479] update signature assistant broken

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358479

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Milian Wolff  ---
This was fixed by Olivier Goffart upstream for clang-3.9 (thanks!).

https://reviews.llvm.org/D19764

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

[kdevelop] [Bug 365635] signature assistant unusable since assistant-ng merge

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365635

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Milian Wolff  ---
afaik this is fixed now, it works. my bug report does not include enough info
even for me to remember what triggered the issue

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

[kdevelop] [Bug 367825] KDevelop 5 freezes while parsing Javascript code

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367825

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Milian Wolff  ---


*** This bug has been marked as a duplicate of bug 355100 ***

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

[kdevelop] [Bug 368270] Crash when pressing ALT + ENTER in assistant dialog

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368270

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/88f4b2998d1e01ac03
   ||48ecf2587acdb3d086f4fc
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Milian Wolff  ---
Git commit 88f4b2998d1e01ac0348ecf2587acdb3d086f4fc by Milian Wolff.
Committed on 05/09/2016 at 15:50.
Pushed by mwolff into branch '5.0'.

Don't lock the duchain while handling navigation widget events.

Only the html generation needs to lock the duchain (or?), thus
remove it elsewhere to not get assertions further down when doing
more complicated stuff like for the signature assistant.

M  +12   -4language/duchain/navigation/abstractnavigationcontext.cpp
M  +1-0language/duchain/navigation/abstractnavigationcontext.h
M  +7-13   language/duchain/navigation/abstractnavigationwidget.cpp

http://commits.kde.org/kdevplatform/88f4b2998d1e01ac0348ecf2587acdb3d086f4fc

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

[kdevelop] [Bug 367690] Git option in RMB is not available after click in any place of versioned file

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367690

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/d641fca76215a7de01
   ||ee1bae59c6269e46c8da79
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Milian Wolff  ---
Git commit d641fca76215a7de01ee1bae59c6269e46c8da79 by Milian Wolff.
Committed on 05/09/2016 at 16:00.
Pushed by mwolff into branch '5.0'.

Properly initialize EditorContext::urls

Fixes querying the git plugin context menu from the editor context
menu, and elsewhere.

M  +5-0language/interfaces/editorcontext.cpp
M  +1-0language/interfaces/editorcontext.h

http://commits.kde.org/kdevplatform/d641fca76215a7de01ee1bae59c6269e46c8da79

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

[kdevelop] [Bug 368270] Crash when pressing ALT + ENTER in assistant dialog

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368270

--- Comment #2 from Milian Wolff  ---
I'm on this

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

[kdevelop] [Bug 368283] Segfault when running multiple unit tests from Unit Tests tool view

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368283

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Milian Wolff  ---
we need a backtrace. Actually, show me this thingy later today and we can debug
it together

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

[kdevelop] [Bug 367926] Maximum number of background parser threads not saved

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367926

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/265b519e919baa4c8a
   ||83e97b44e6c786fc18b8f8
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Milian Wolff  ---
Git commit 265b519e919baa4c8a83e97b44e6c786fc18b8f8 by Milian Wolff.
Committed on 05/09/2016 at 14:17.
Pushed by mwolff into branch '5.0'.

Save background parser settings to config

M  +4-0shell/settings/bgpreferences.cpp

http://commits.kde.org/kdevplatform/265b519e919baa4c8a83e97b44e6c786fc18b8f8

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

[kdevelop] [Bug 367926] Maximum number of background parser threads not saved

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367926

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[kdevelop] [Bug 368105] Wrong type is deduced for type auto

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368105

--- Comment #4 from Milian Wolff  ---
Look into the problems toolview, has there been errors about files not being
found or anything else serious? If that happens, it can confuse clang
completely (esp. older versions). So if you suffer from this, double check
that.

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

[kdevelop] [Bug 368264] Man pages plugin broken

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368264

Milian Wolff  changed:

   What|Removed |Added

   Target Milestone|--- |5.0.1
   Severity|normal  |major
   Priority|NOR |VHI

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

[kdevelop] [Bug 331227] crash on launch: [Project::projectFileManager -> extension]

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=331227

Milian Wolff  changed:

   What|Removed |Added

 CC||marku...@gmx.de

--- Comment #8 from Milian Wolff  ---
*** Bug 348246 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 368270] Crash when pressing ALT + ENTER in assistant dialog

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368270

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Milian Wolff  ---
void AbstractNavigationWidget::accept() {
  DUChainReadLocker lock( DUChain::lock() );
...

void AdaptSignatureAction::execute()
{
ENSURE_CHAIN_NOT_LOCKED

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

[kdevelop] [Bug 368278] Crash when starting project's Build operation while Install was in progress

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368278

Milian Wolff  changed:

   What|Removed |Added

 Resolution|FIXED   |WAITINGFORINFO

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

[kdevelop] [Bug 368278] Crash when starting project's Build operation while Install was in progress

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368278

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Milian Wolff  ---
The backtrace indicates that you quit the application. Is that not what you
did? The title of this bugreport says something completely different. Hm I
rather think that this is a setup issue on your side

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

[kdevelop] [Bug 348246] KDevelop crashes when reloading an already open PHP project

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348246

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Milian Wolff  ---


*** This bug has been marked as a duplicate of bug 331227 ***

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

[kdevelop] [Bug 368257] Crashes when the next line of "TODO" is edit.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368257

--- Comment #2 from Milian Wolff  ---
Git commit 504dbe08af18c36f13277af9d0616ce12bd2b214 by Milian Wolff.
Committed on 05/09/2016 at 13:37.
Pushed by mwolff into branch '5.0'.

Try to add a test for the reparse crash.

Sadly, the test passes and I have no clue why...

M  +26   -0duchain/tests/duchain_multiplefiles.cpp
M  +1-0duchain/tests/duchain_multiplefiles.h

http://commits.kde.org/kdev-php/504dbe08af18c36f13277af9d0616ce12bd2b214

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

[kdevelop] [Bug 368257] Crashes when the next line of "TODO" is edit.

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368257

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||-php/fa052cacf5f9d63ba9c6ba
   ||7a2ec82a50c5bbd31d
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Milian Wolff  ---
Git commit 504dbe08af18c36f13277af9d0616ce12bd2b214 by Milian Wolff.
Committed on 05/09/2016 at 13:37.
Pushed by mwolff into branch '5.0'.

Try to add a test for the reparse crash.

Sadly, the test passes and I have no clue why...

M  +26   -0duchain/tests/duchain_multiplefiles.cpp
M  +1-0duchain/tests/duchain_multiplefiles.h

http://commits.kde.org/kdev-php/504dbe08af18c36f13277af9d0616ce12bd2b214

--- Comment #3 from Milian Wolff  ---
Git commit fa052cacf5f9d63ba9c6ba7a2ec82a50c5bbd31d by Milian Wolff.
Committed on 05/09/2016 at 13:37.
Pushed by mwolff into branch '5.0'.

Don't crash by accessing invalid offsets while extracting todos.

M  +6-0parser/php.g

http://commits.kde.org/kdev-php/fa052cacf5f9d63ba9c6ba7a2ec82a50c5bbd31d

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

[kate] [Bug 367466] crash on invalid text line access in KateLayoutCache::textLayout

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367466

Milian Wolff  changed:

   What|Removed |Added

   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
  Component|general |folding
 Status|UNCONFIRMED |CONFIRMED
Product|kdevelop|kate
 Ever confirmed|0   |1
Version|unspecified |Git

--- Comment #2 from Milian Wolff  ---
yes

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

[kdevelop] [Bug 367659] Build fails at cppducontext.h:655:22: error: ... const [with BaseContext = KDevelop::DUContext]’ marked ‘override’, but does not override

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367659

--- Comment #4 from Milian Wolff  ---
Note: According to your log, you try to pass BUILD_clang=yes, but that is not a
valid option. But by passing -DBUILD_cpp=yes you disable the clang build.
Remove that option.

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

[kdevelop] [Bug 367659] Build fails at cppducontext.h:655:22: error: ... const [with BaseContext = KDevelop::DUContext]’ marked ‘override’, but does not override

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367659

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/f4b5b7538be64328cf8462
   ||ee438caaac6c0907aa

--- Comment #3 from Milian Wolff  ---
Git commit f4b5b7538be64328cf8462ee438caaac6c0907aa by Milian Wolff.
Committed on 22/08/2016 at 10:47.
Pushed by mwolff into branch '5.0'.

Fix compile

M  +4-2languages/cpp/cppduchain/cppducontext.cpp
M  +2-1languages/cpp/cppduchain/cppducontext.h

http://commits.kde.org/kdevelop/f4b5b7538be64328cf8462ee438caaac6c0907aa

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