Bug 375233 - Cannot use 'try' with exceptions disabled.
Summary: Cannot use 'try' with exceptions disabled.
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (show other bugs)
Version: 5.0.3
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-18 13:37 UTC by Benjamin
Modified: 2022-12-26 05:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Seeing error even when code compiles fine. (7.05 KB, image/png)
2017-01-18 13:37 UTC, Benjamin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin 2017-01-18 13:37:43 UTC
Created attachment 103479 [details]
Seeing error even when code compiles fine.

With new clang-based c++ support, all my 'try's are underlined with a pop-up stating that I "cannot use 'try' with exceptions disabled". The build system is setup to allow exceptions, so the code compiles fine, but it still shows up in the "Problems" area.

Running Kdevelop 5.0.3 on Windows 10.
Comment 1 Benjamin 2017-02-16 21:33:55 UTC
Is there a setting somewhere to easily turn on and off exceptions, perhaps I "solved" my problem incorrectly and my solution was out of sync with what the program was expecting?
Comment 2 Sven Brauch 2017-02-16 21:45:18 UTC
Can you try adding -fcxx-exceptions to the project configuration, Language Support, C/C++ Parser, Custom text edit?

Otherwise export KDEV_CLANG_DISPLAY_DIAGS=1 and then looking at the output might be interesting.
Comment 3 argonel 2018-06-15 17:17:31 UTC
I've just had this in 5.2.1 on Linux. I'm using KDE_TARGET_ENABLE_EXCEPTIONS from ECM, and I had added that to the relevant CMakelists.txt since the last time I opened KDevelop. Adding -fcxx-exceptions had no effect.

After quitting and reopening KDevelop the complaint was gone, but after reverting to the default C++ profile it didn't come back.
Comment 4 Justin Zobel 2022-11-26 00:13:49 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-11 05:06:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-26 05:20:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!