Hi,
Please welcome a new bug-fix update: CLion 2019.1.3! Build 191.7141.37 is now available to download from our website, via the Toolbox App, or via snap (for Ubuntu). A patch-update will be available shortly.
Here are the highlights:
- CLion can now work with header guards that use several define patterns (CPP-15736).
- CMake 3.14.3 is now bundled.
- The exception, when Google Sanitizers were launched from CLion, is fixed.
Full release notes are here.
Your CLion Team
JetBrains
The Drive to Develop
clion freeze a lot on my mac when update to 2019.1
When UI is freezing, there are thread dumps generated automatically in logs directory (Help | Show Logs in Finder). Please pack some fresh dumps and send to our support (clion-support@jetbrains.com) for further investigation.
Hello. After i call hierarchy from action menu (Command+Shift+A), this command no longer works.
Example output:
ditto(1) – copy directory hierarchies, create and extract archives
find(1) – walk a file hierarchy
hier(7) – layout of filesystems
iwidgets_hierarchy(n), iwidgets::hierarchy(n) – Create and manipulate a hierarchy widget
mdimport(1) – import file hierarchies into the metadata datastore
mtree(8) – map a directory hierarchy
pax(1) – read and write file archives and copy directory hierarchies
torque(1) – ./” ./” Launches one or more child processes, each of which performs a series of bandwidth intensive operations, and after completion reports the bandwidth actually achieved by each operation during a period when all operation streams were executing simultaneously. ./” ./”
ttk::treeview(ntcl) – hierarchical multicolumn data display widget
Not sure, what this output sample means. Can you maybe explain?
When i press again this shortcut i see console popup from this message, but i can call action menu again only after restart clion
Console – do you mean your system console? Maybe the shortcut is overwritten by your system settings?
No. I can’t call action popup again.
1. I press shortcut for call actions menu. I see this menu
2. Type in search field hierarchy and i see hierarchy menu
3. Press again shortcut for call action menu and i see yellow console popup from this message.
Could you please create a ticket in https://youtrack.jetbrains.com/issues/CPP and attach a few screenshots or a video?
Ok.
ticket: https://youtrack.jetbrains.com/issue/CPP-16225
Thanks. We’ll proceed in the ticket.
I tried to evaluate again, and it still is not usable for my main project
too slow debugger. After stopping at first breakpoint it thinks for a minute or even longer before I can do any other action. This doesn’t happen in Xcode. All tips from how to enhance debugging experience don’t help, i turned off all data views & renderers .. no luck.
If you are patient enough though after this first giant delay it works well without slowness, but the time is big enough in Xcode I relaunch program several times …
Could you please reproduce the issue and collect debug logs when this happens? The instruction on how to turn on the additional debugger logging info is here: https://intellij-support.jetbrains.com/hc/en-us/articles/206560589-What-to-do-if-debugger-doesn-t-work-as-expected-
Then please send to our support or to the newly created issue in the bug tracker. We’ll take a look at what might cause such a delay, that’s definitely not normal.
Done.
Thank you. Have you sent to the support? Or to the tracker? If tracker, could you then please point me with the link? I’ll check it out.
Hi Anastasia, when can we expect 2019.2 EAP? I write a lot of CMake lately and CPP-15515 is killing me, it’s a bad coincidence.:)
Thanks
Should start soon in May, however I can’t provide any more exact estimate on this for now.
Hi,
Do the CLion developers regularly test Qt-based projects?
It seems that there’s always something that’s broken in Qt-using code.
For example, in the current release, QStringLiteral(“”) says “Use of undeclared identifier ‘QStringLiteral'”.
If I disable clangd server, QStringLiteral itself is no longer red, but using raw string literals inside it produce this error: “Error after macro substitution: Incompatible types in initializer: Initializer string is too long for array of chars.”
Note that there are quite a few other nonsensical errors with clangd – see the example project I’m linking to.
Unfortunately, stuff like this makes the IDE really hard to use – the whole file is highlighted with red squiggles.
Here is a dead-simple example project (see main.cpp for QStringLiteral, main_window.cpp for other nonsensical errors with clangd):
https://drive.google.com/file/d/1v9yAIqYoedTPP8x2YDAdCZ-3VkL8Ki1W/view?usp=sharing
Screenshots:
https://imgur.com/a/9sO1BfZ
We do check various projects in tests and in manual smoke tests before publishing the build. We’ll see what’s going on for the Qt code there, thanks.
On which environment/platform/toolchain are you?
We actually failed to reproduce the problem with clangd enabled (checked clang and gcc). So it would be useful to know your toolchain and environment.
With clangd disables looks similar to https://youtrack.jetbrains.com/issue/CPP-12194 and https://youtrack.jetbrains.com/issue/CPP-11534. But should be eliminated with clangd on. Let’s investigate the issue with clangd enabled first.
Hi Anastasia,
Thanks a lot for the investigation. For now I enabled clangd.
CLion settings:
https://imgur.com/a/IDQDrEN
These are my platform details:
OpenSUSE Linux 15.0.
gcc-7-lp150.1.50.x86_64 (system-bundled),
gcc8-8.3.1+r269383-lp150.67.1.x86_64 (from OBS),
clang7-7.0.1-lp150.24.2.x86_64 (from OBS),
glibc-2.26-lp150.11.9.1.x86_64 (system-bundled),
libqt5-qtbase-devel-5.9.4-lp150.4.8.x86_64 (system-bundled).
The opensuse-bundled gcc 7 is the system compiler. Switching to a clang-based toolchain doesn’t affect the errors – they’re still there.
Control-clicking “QStringLiteral” actually takes me to qstring.h, where no errors are highlighted. Makes me wonder why it’s “undeclared” if clion finds it.
I tried with a clean CLion configuration – the errors are still there.
Maybe it’s related to the Qt version (5.9.4)? I’m using the one supplied with the distribution – can’t upgrade it without upgrading KDE as well.
Thanks
Hi, Alexander!
I tried to reproduce your issue in a similar environment and got a bit different errors, however, we believe they have the same root cause.
I filed a bug regarding the matter https://youtrack.jetbrains.com/issue/CPP-16248, please follow it to get updates.
Thanks a lot!
very nice thanks.
can i install on win 10 64bit?
yes, it works on 64b windows