blocks|key|2751205|text|事实证明，可执行文件是用以下CMake选项编译的(在脚本中更低的位置)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2751206|SET(CMAKE_C_FLAGS_DEBUG+"-D_DEBUG")|code-block|syntax|javascript|2751207|这破坏了CLion的调试功能(也破坏了gdb的大部分调试功能)|offset|length|style|CODE|2751208|entityMap^0|0|0|J|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

As it has turned out, the executable was compiled with following CMake options (further down in the script):

<pre><code>SET(CMAKE_C_FLAGS_DEBUG "-D_DEBUG")
</code></pre>

This was breaking debug functionality for CLion (it was also breaking most of the debug functionality of <code>gdb</code>)

blocks|key|724330|text|我今天也有同样的问题。我发现该项目的配置没有设置为Debug。在将配置设置为Debug之后，所有断点都会被击中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|724331|请确保您有以下配置：|724332|选择MenuItem+Run/EditConfigurations|unordered-list-item|724333|选择正确的Target|724334|选择Debug作为Configuration|724335|现在断点应该被击中。|724336|entityMap^0|P|5|12|5|0|0|B|M|0|5|6|0|2|5|9|D|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|K|3|L|5|J|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|M|3|N|5|J|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|19|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|R|$]]

I had the same issue today. I figured out that the configuration for the project was not set to <code>Debug</code>. After setting the configuration to <code>Debug</code> all the breakpoints are hit.

Please ensure that you have following configuration:

<ul>
<li>Select the MenuItem <code>Run/EditConfigurations</code></li>
<li>Select the right <code>Target</code></li>
<li>Select <code>Debug</code> as <code>Configuration</code></li>
</ul>

Now the breakpoints should be hit.

blocks|key|724346|text|我也有同样的问题。由于2016.3+CLion更改了CMake工作流，因此一次只允许一次配置clion新工作流|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|724347|解决方案是文件->设置->构建、执行、部署->更改生成配置|724348|entityMap|0|LINK|mutability|MUTABLE|url|https://blog.jetbrains.com/clion/2016/10/clion-2016-3-eap-cmake-overload-resolution/^0|1A|9|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I also had the same Problem. Since 2016.3 CLion changed the CMake workflow so that only one configuration is allowed at one time <a href="https://blog.jetbrains.com/clion/2016/10/clion-2016-3-eap-cmake-overload-resolution/" rel="nofollow noreferrer">clion new workflow</a>

The solution is File -> Settings -> Build, Excution, Deployment -> change the build configuration

blocks|key|2751224|text|如果这对其他人有帮助的话，那么我(有些尴尬)的问题就是我是在点击Run而不是Debug。因此，在“运行”菜单中，不要使用“播放”图标，而是选择可爱的bug图标。选择Run会导致它自动生成非调试生成，这样断点就无法工作。一旦我开始选择bug图标，断点就像一种魅力。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2751225|entityMap^0|W|3|12|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In case this helps someone else, it turned out that my (somewhat embarrassing) issue was that I was hitting <code>Run</code> instead of <code>Debug</code>. So in the Run menu don't use the play icon, instead choose the cute bug icon instead. Choosing Run was causing it to automatically build the non-debug build so breakpoints wouldn't work. Once I started choosing the bug icon, the breakpoints worked like a charm.

blocks|key|387943|text|我也有过同样的问题。我注意到，每次单击debug选项时，"Antimalware+Executable“进程就会启动。我在windows中为MinGW文件夹创建了一个排除，它运行得很好.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|387944|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue. I noticed that every time I click the debug option, the "Antimalware Service Executable" process starts. I created an exclusion for MinGW folder in windows Defender and it worked fine...

blocks|key|391240|text|在2019.3中，结果是CLion/首选项/构建、执行、部署/CMake/Build类型/Debug。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391241|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In 2019.3, it turns out to be CLion/Preference/Build,Execution,Deployment/CMake/Build type/Debug.

blocks|key|724493|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724494|📷|atomic|offset|length|724495|724496|正如minecrawler在github中所说的，如果您的操作系统是linux，那么您应该设置：|724497|文件/设置/构建、执行、部署/Tllochains/Debugger从绑定的GEB或gdb到绑定的LLDB。|724498|我试过了，而且用词很好！|724499|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/a5ef426f8b0c867442e24969252c2413.png|imageAlt^0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|G|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

<img src="https://i.stack.imgur.com/nuseM.png" alt="">

Just like minecrawler said in github, if your os is linux, your should set：

file/Settings/Build,Execution,Deployment/Tllochains/Debugger from Bundled GEB or gdb to Bundled LLDB.

I tried and it worded！

blocks|key|724520|text|在我的例子中(Linux+/+Ubuntu)，问题在某种程度上与挂载目录有关。该项目最初是在CLion从/media/username/ssd/repo/git/projectname开始的。断点总是被消息No+executable+code+is+associated+with+this+line禁用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|724521|然后，我从一个符号链接目录~/git+->+/media/username/ssd/repo/git中打开了同一个项目，断点开始正常工作。|724522|entityMap^0|1G|14|2V|1B|0|D|5|M|S|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

In my case (Linux / Ubuntu) the problem was somehow related to mounted directory.
The project was initially opened in CLion from <code>/media/username/ssd/repo/git/projectname</code>. The breakpoints were always disabled with message <code>No executable code is associated with this line</code>.

Then I opened the same project from a symlinked directory
<code>~/git</code> -> <code>/media/username/ssd/repo/git</code> and the breakpoints began to work fine.

blocks|key|724573|text|在我的例子中，我的CMake选项CMAKE_BUILD_TYPE已经设置为在CMake设置上调试。但是，这是CMakeLists.txt中的命令集(CMakeLists.txt发行版)，该命令集被git合并，并在执行时覆盖CMake设置。当CMake调试控制台显示-DCMAKE_BUILD_TYPE=Debug时，我不知道早些时候|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724574|当我将其更改为set(CMAKE_BUILD_TYPE调试)时，断点再次被击中。|724575|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case my CMake option CMAKE_BUILD_TYPE was already set to DEBUG on CMake Settings. However, it was the command set(CMAKE_BUILD_TYPE Release) in the CMakeLists.txt, which was merged by git pull and overrode the CMake Settings while execution. I could not figure out earlier as CMake Debug console was showing -DCMAKE_BUILD_TYPE=Debug

When I changed it to set(CMAKE_BUILD_TYPE Debug) breakpoints were hit again.

blocks|key|2751430|text|我的项目路径中有一个逗号。去掉逗号为我解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2751431|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a comma in my project path. Removing the comma fixed the problem for me.

blocks|key|2751476|text|我的问题是-ffile-prefix-map标志。一旦我把它取下来，一切都很好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2751477|见https://youtrack.jetbrains.com/issue/CPP-23159和https://youtrack.jetbrains.com/issue/CPP-15850|2751478|entityMap|0|LINK|mutability|MUTABLE|url|https://youtrack.jetbrains.com/issue/CPP-23159|1|https://youtrack.jetbrains.com/issue/CPP-15850^0|5|H|0|1|1A|0|1C|1A|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]|$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

My problem was with the <code>-ffile-prefix-map</code> flag. Once I removed it, everything worked fine.
See <a href="https://youtrack.jetbrains.com/issue/CPP-23159" rel="nofollow noreferrer">https://youtrack.jetbrains.com/issue/CPP-23159</a> and <a href="https://youtrack.jetbrains.com/issue/CPP-15850" rel="nofollow noreferrer">https://youtrack.jetbrains.com/issue/CPP-15850</a>

blocks|key|391344|text|在我的例子中，我必须编辑该文件，以便重新编译所有内容，而不是使用缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391345|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I had to edit the file so that everything was compiled again instead of using cache.

blocks|key|2751548|text|万一这对其他人有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2751549|在我的例子中，我必须将-DCMAKE_BUILD_TYPE选项显式地设置为Debug，设置->构建、执行、部署->+CMake|offset|length|style|CODE|2751550|​|2751551|📷|atomic|2751552|2751553|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/614966e37aaf978ee6990b9449de1095.png|imageAlt^0|0|B|I|11|5|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|M|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

In case this helps someone else:
In my case I had to set the <code>-DCMAKE_BUILD_TYPE</code> option to <code>Debug</code> explicitly in Settings -&gt; Build, Execution, Deployment -&gt; CMake
<a href="https://i.stack.imgur.com/gnhLu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/gnhLu.png" alt="My case" /></a>

blocks|key|388102|text|在我的例子中，问题是忘记注释掉cmakelist中的优化选项add_definitions(-O3)。它让编译器发布。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|388103|entityMap^0|U|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case, the problem is forget to comment out optimize option <code>add_definitions(-O3)</code> in cmakelists. which let compiler go release.

blocks|key|2751635|text|我有一个不同的问题，使我的断点没有被击中。我用CLion开发了嵌入式应用程序和本地CLion控制台应用程序。对于嵌入式工作，需要为所选的首选项/工具链设置GDB。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2751636|对于调试控制台应用程序，需要在首选项/工具链中选择LLDB。如果它留在GDB上，我的断点就不能工作。在这里设置为LLDB：|2751637|​|2751638|📷|atomic|offset|length|2751639|2751640|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/abe5ca1bfbbd30f6d19c1d69ca8f1c43.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

I had a different issue that caused my breakpoints not to be hit. I develop both embedded apps and native MacOS console apps with CLion. For the embedded work, GDB needs to be set for your selected Preferences/Toolchains.
For debugging console apps LLDB needs to be selected in Preferences/Toolchains. If it is left on GDB, my breakpoints don't work. Set to LLDB here:
<a href="https://i.stack.imgur.com/gZAyt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/gZAyt.png" alt="enter image description here" /></a>

I'm trying to debug an executable which has been created with CMake configuration

<pre><code>SET(CMAKE_BUILD_TYPE Debug)
</code></pre>

However, CLion does not hit any breakpoints. What could be the problem?

Why are my breakpoints not hit in CLion?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在调试一个用CMake配置创建的可执行文件SET(CMAKE_BUILD_TYPE Debug)然而，CLion没有触及任何断点。有什么问题吗？

问为什么我的断点没有在CLion中被击中？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么我的断点没有在CLion中被击中？EN