blocks|key|1342335|text|您可以创建一个虚拟变量并将其设置为不同的值。然后可以使用条件监视点。示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1342336|#include+<stdio.h>
static+volatile+int+loc;
int+main()
{
++++loc+=+1;
++++puts("hello+world");
++++loc+=+2;
++++return+0;
}|code-block|syntax|javascript|1342337|(gdb)+watch+loc+if+loc+==+2
Hardware+watchpoint+1:+loc
(gdb)+r
Starting+program:+/tmp/a.out+
hello+world

Hardware+watchpoint+1:+loc

Old+value+=+1
New+value+=+2
main+()+at+test.c:8
8+++++++return+0;|1342338|当然，您可以将赋值包装在宏中，以便只在调试生成中获得赋值。常用的注意事项:优化和内联可能会受到影响。|1342339|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|D|7|O|8|@]|9|@]|A|$E|F]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You could create a dummy variable and set it to different values. Then you can use conditional watchpoints. Example:
<pre><code>#include &lt;stdio.h&gt;
static volatile int loc;
int main()
{
 loc = 1;
 puts(&quot;hello world&quot;);
 loc = 2;
 return 0;
}
</code></pre>
<hr />
<pre><code>(gdb) watch loc if loc == 2
Hardware watchpoint 1: loc
(gdb) r
Starting program: /tmp/a.out 
hello world

Hardware watchpoint 1: loc

Old value = 1
New value = 2
main () at test.c:8
8 return 0;
</code></pre>
You can of course wrap the assignment in a macro so you only get it in debug builds. Usual caveats apply: optimizations and inlining may be affected.

blocks|key|343434|text|您可以在想要断点的每一行插入一个#warning，然后有一个脚本来解析编译器消息中的文件和行号，并编写一个.gdbinit文件，在这些位置放置断点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|343435|entityMap^0|G|8|1H|8|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|$]]

You could insert a <code>#warning</code> at each line where you want a breakpoint, then have a script to parse the file and line numbers from the compiler messages and write a <code>.gdbinit</code> file placing breakpoints at those locations.

blocks|key|343495|text|使用SDT+(静态定义跟踪)探测点似乎可以满足所有需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|343496|GDB+文档链接到如何定义探测的示例。|offset|length|343497|示例使用：(gdb)+break+-probe-stap+my_probe+(这应该记录在GDB断点部分中，但目前没有)。|style|CODE|343498|entityMap|0|LINK|mutability|MUTABLE|url|https://sourceware.org/gdb/current/onlinedocs/gdb/Static-Probe-Points.html|1|https://blog.sergiodj.net/2012/10/27/gdb-and-systemtap-probes-part-2.html|2|https://sourceware.org/gdb/current/onlinedocs/gdb/Set-Breaks.html#Set-Breaks^0|0|4|2|0|0|5|W|0|4|1|19|7|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@$D|11|E|12|H|I]]|9|@$D|13|E|14|1|15]|$D|16|E|17|1|18]]|A|$]]|$1|J|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]]]

Using SDT (Statically Defined Tracing) probe points appears to satisfy all the requirements.
GDB <a href="https://sourceware.org/gdb/current/onlinedocs/gdb/Static-Probe-Points.html" rel="nofollow noreferrer">documentation</a> links to examples of how to define the probes.
<a href="https://blog.sergiodj.net/2012/10/27/gdb-and-systemtap-probes-part-2.html" rel="nofollow noreferrer">Example use</a>: <code>(gdb) break -probe-stap my_probe</code> (this should be documented in the <a href="https://sourceware.org/gdb/current/onlinedocs/gdb/Set-Breaks.html#Set-Breaks" rel="nofollow noreferrer">GDB breakpoints section</a>, but currently isn't).

blocks|key|1342457|text|使用python在源文件中搜索一些预定义的标签，并在那里使用设置断点：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1342458|def+break_on_labels(source,+label):
++++"""add+breakpoint+on+each+SOURCE+line+containing+LABEL"""
++++with+open(source)+as+file:
++++++++l+=+0
++++++++for+line+in+file:
++++++++++++l+=+l+%2B+1
++++++++++++if+label+in+line:
++++++++++++++++gdb.Breakpoint(source=source,+line=l)

main_file+=+gdb.lookup_global_symbol("main").symtab.fullname()
break_on_labels(main_file,+"BREAK-HERE")|code-block|syntax|javascript|1342459|示例：|1342460|int+main(void)
{
++int+a+=+15;
++a+=+a+%2B+23;+//+BREAK-HERE
++return+a;
}|1342461|entityMap|0|LINK|mutability|MUTABLE|url|https://sourceware.org/gdb/current/onlinedocs/gdb/Breakpoints-In-Python.html^0|U|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Use python to search a source file for some predefined labels, and <a href="https://sourceware.org/gdb/current/onlinedocs/gdb/Breakpoints-In-Python.html" rel="nofollow noreferrer">set breakpoints</a> there:
<pre><code>def break_on_labels(source, label):
 &quot;&quot;&quot;add breakpoint on each SOURCE line containing LABEL&quot;&quot;&quot;
 with open(source) as file:
 l = 0
 for line in file:
 l = l + 1
 if label in line:
 gdb.Breakpoint(source=source, line=l)

main_file = gdb.lookup_global_symbol(&quot;main&quot;).symtab.fullname()
break_on_labels(main_file, &quot;BREAK-HERE&quot;)
</code></pre>
Example:
<pre><code>int main(void)
{
 int a = 15;
 a = a + 23; // BREAK-HERE
 return a;
}
</code></pre>

Problem:
I want to be able to put different potentially unique or repeated &quot;tags&quot; across my C code, such that I can use them in gdb to create breakpoints.
Similar Work:
<ul>
<li>Breakpoints to line-numbers: The main difference with breakpoints on source lines, is that if the code previous to the tag is modified in such a way that it results in more or less lines, a reference to the tag would still be semantically correct, a reference to the source line would not.
</li>
<li>Labels: I am coming from my previous question, <a href="https://stackoverflow.com/questions/70086938/how-to-tell-gcc-to-keep-my-unused-labels">How to tell gcc to keep my unused labels?</a>, in which I preconceived the idea that the answer was to insert labels. Upon discussion with knowledgeable members of the platform, I was taught that label's names are not preserved after compilation. Labels not used within C are removed by the compiler.
</li>
<li>Injecting asm labels: Related to the previous approach, if I inject asm code in the C source, certain problems arise, due to inline functions, compiler optimizations, and lack of scoping. This makes this approach not robust.
</li>
<li>Define a dummy function: On this other question, <a href="https://stackoverflow.com/questions/9671560/set-gdb-breakpoint-in-c-file">Set GDB breakpoint in C file</a>, there is an interesting approach, in which a &quot;dummy&quot; function can be placed in the code, and then add a breakpoint to the function call. The problem with this approach is that the definition of such function must be replicated for each different tag.
</li>
</ul>
Is there a better solution to accomplish this? Or a different angle to attack the presented problem?

How to 'tag' a location in a C source file for a later breakpoint definition?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

问题:我希望能够在C代码中放置不同的可能唯一的或重复的“标记”，这样我就可以在gdb中使用它们来创建断点。类似工作：行号的断点：与源行上断点的主要区别是，如果对标记之前的代码进行修改，使其产生或多或少的行，则对标记的引用在语义上仍将是正确的，而对源行的引用则不会。标签：我来自于我之前的问题，在这个问题中，我先入为主地认...

问如何标记C源文件中的位置以供以后的断点定义使用？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何标记C源文件中的位置以供以后的断点定义使用？EN