https://bugs.kde.org/show_bug.cgi?id=455533
Igor Kushnir changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #20 from Sigbjorn ---
(In reply to Gabriele Menna from comment #19)
> In my setup, this bug was caused by duplicated add_test statements.
Yes, this is according to the minimal example provided, that triggers the
errors. Two test-suites(as
https://bugs.kde.org/show_bug.cgi?id=455533
Gabriele Menna changed:
What|Removed |Added
CC||gab...@gmail.com
--- Comment #19 from
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #18 from zb4ng ---
(In reply to Igor Kushnir from comment #17)
> This bug report is about a crash on exit, not freeze. Could you be
> experiencing Bug 379669?
You are right. I am sorry, I have missed this while reading...
--
You are
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #17 from Igor Kushnir ---
(In reply to zb4ng from comment #16)
> after exiting kdevelop: the CPU-load of kdevelop is maxed out and it has a
> bash child process
> KILL (kill -9) is necessary (TERM (kill -15) has no effect)
This bug report
https://bugs.kde.org/show_bug.cgi?id=455533
zb4ng changed:
What|Removed |Added
CC||zb...@arcor.de
--- Comment #16 from zb4ng ---
just
https://bugs.kde.org/show_bug.cgi?id=455533
Milian Wolff changed:
What|Removed |Added
CC||fabian.kis...@gmx.de
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #14 from Igor Kushnir ---
Thanks for the great sample project. Just reproduced the crash on KDevelop exit
at the first try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #13 from Sigbjorn ---
The provided example is minimal, and emulates the effects when using multiple
test binaries, or delayed test-generation that gives similar effects for even a
single binary test project.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #12 from Sigbjorn ---
Created attachment 14
--> https://bugs.kde.org/attachment.cgi?id=14=edit
minimal example that illustrates the crash
also available here https://gitlab.com/sigbjorn.helset/kdev-issue-support.git
--
You are
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #11 from Sigbjorn ---
(In reply to Igor Kushnir from comment #10)
> (In reply to Sigbjorn from comment #9)
> > (In reply to Igor Kushnir from comment #7)
> > > The test suite code is somewhat messy and buggy. I have started fixing it
> > >
https://bugs.kde.org/show_bug.cgi?id=455533
Igor Kushnir changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #9 from Sigbjorn ---
(In reply to Igor Kushnir from comment #7)
> The test suite code is somewhat messy and buggy. I have started fixing it
> more than a year ago, but sadly postponed that work in favor of other
> fixes/improvements. If you
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #8 from Sigbjorn ---
Investigations:
Using the doctest (gitlab.com/doctest), generates test-cases, that are picked
up and enlisted by the test executable it self.
In doctest, there test might be grouped into test-suites, and test-cases are
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #7 from Igor Kushnir ---
The test suite code is somewhat messy and buggy. I have started fixing it more
than a year ago, but sadly postponed that work in favor of other
fixes/improvements. If you want to try and fix this issue, I could
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #6 from Sigbjorn ---
Based on the stack/listing etc. it seems to be related to the cmake-manager
test suite handling.
Other observations of interest:
(0) Re-generating cmake after cmake-file changes, also crashes the kdevelop
(will check
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #5 from Sigbjorn ---
(In reply to Sigbjorn from comment #4)
> (In reply to Sigbjorn from comment #3)
> > .. after downloading debuginfo, repeating the crash procedure, and using
> > gdb,(konqi seems to disable/or not read .gdb.ini file,
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #4 from Sigbjorn ---
(In reply to Sigbjorn from comment #3)
> .. after downloading debuginfo, repeating the crash procedure, and using
> gdb,(konqi seems to disable/or not read .gdb.ini file, will sort out that
> later),,
> here seems to be
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #3 from Sigbjorn ---
.. after downloading debuginfo, repeating the crash procedure, and using
gdb,(konqi seems to disable/or not read .gdb.ini file, will sort out that
later),,
here seems to be the intersting spots:
#7 0x7fc16bf7faad
https://bugs.kde.org/show_bug.cgi?id=455533
--- Comment #2 from Sigbjorn ---
(In reply to Igor Kushnir from comment #1)
> > #5 0x7f81bb18e2d4 in () at
> > /usr/lib/qt/plugins/kdevplatform/36/kdevcmakemanager.so
> Could you please build KDevelop with debug symbols to generate a more useful
https://bugs.kde.org/show_bug.cgi?id=455533
Igor Kushnir changed:
What|Removed |Added
CC||igor...@gmail.com
--- Comment #1 from Igor
21 matches
Mail list logo
