https://bugs.kde.org/show_bug.cgi?id=376149
Dennis Schridde changed:
What|Removed |Added
CC||devuran...@gmx.net
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #14 from Kevin Funk ---
RelWithDebInfo should be sufficient. But you also need to make sure that
LLVM_ENABLE_ASSERTIONS:BOOL is not ON.
Please check whether your compiler invocations contain -DNDEBUG.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #13 from Johannes Hirte ---
(In reply to Kevin Funk from comment #12)
> Sorry, one remark missing: if you use -DCMAKE_BUILD_TYPE=Release or
> ...=RelWithDebInfo, NDEBUG will be defined.
clang/llvm was build with -DCMAKE_BUILD_TYPE=RelWithDe
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #12 from Kevin Funk ---
Sorry, one remark missing: if you use -DCMAKE_BUILD_TYPE=Release or
...=RelWithDebInfo, NDEBUG will be defined.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #11 from Kevin Funk ---
assert() itself takes NDEBUG into account. In other words, if NDEBUG is defined
when assert.h is included, assert() does nothing.
See: http://en.cppreference.com/w/c/error/assert
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #9 from Kevin Funk ---
Sorry, forget my previous comment. LLVM_ENABLE_ASSERTIONS:BOOL is only useful
for *enabling* assertions, it won't help for *disabling* them.
If you want to disable assertions you need -DCMAKE_BUILD_TYPE=RelWithDebInfo
https://bugs.kde.org/show_bug.cgi?id=376149
Kevin Funk changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #8 from Kevin Funk ---
For the upstream build you need to pass -DLLVM_ENABLE_ASSERTIONS:BOOL=OFF to
cmake, fwiw
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #7 from Johannes Hirte ---
(In reply to Kevin Funk from comment #6)
> Note: We don't recommend to build Clang/LLVM with assertions enabled. It
> triggers on a lot of issues in our experience, most of them non-fatal for us.
>
> Do you get a
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #6 from Kevin Funk ---
Note: We don't recommend to build Clang/LLVM with assertions enabled. It
triggers on a lot of issues in our experience, most of them non-fatal for us.
Do you get a crash with assertions disabled?
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=376149
--- Comment #5 from Johannes Hirte ---
two clang bugreports that seem related:
https://bugs.llvm.org//show_bug.cgi?id=22938
https://bugs.llvm.org//show_bug.cgi?id=21905
Still not sure if this is a clang-bug or kdevelop is miss-using something. At
leas
https://bugs.kde.org/show_bug.cgi?id=376149
pavel kropitz changed:
What|Removed |Added
CC||univ...@fu-solution.com
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=376149
Johannes Hirte changed:
What|Removed |Added
Summary|segfault in |KDevelop crash during
|KDeve
15 matches
Mail list logo
