不存在跟踪点时的 gdb 行为

发布于 2024-11-03 17:55:17 字数 1004 浏览 0 评论 0原文

在使用调试程序时,我遇到了一种特殊的行为。我正在远程服务器上运行一个进程并调试该程序。为此我可以使用跟踪点。

我没有指定任何跟踪点。现在,当我执行 tstart 来启动跟踪实验时,它不会 crib,我会得到 he (gdb) 提示。我做了这样的事情:

(gdb) target remote 172.24.0.7:1234                                     
Remote debugging using 172.24.0.7:1234                                
0x00000000 in ?? ()                                                     
(gdb) info tra                                                        
No tracepoints.                                                       
(gdb) symbol-file /usr/local/bin/mybin1                             
Reading symbols from /usr/local/bin/ee/mybin1...done.                   
(gdb) info function  

<< list of functions from mybin1 >> 


(gdb) info tra                                                          
No tracepoints.                                                       
(gdb) tstart                                                          
(gdb)

我想知道这是否是 gdb 的预期行为?

提前致谢。

While debugging a program using I came across a pecular behavior. I am running a process on the remote server and debug the program. For this I can use tracepoints.

I did not specify any trace point. And now when I do a tstart to start the trace experiment, it does not crib, I get he (gdb) prompt back.I did something like this:

(gdb) target remote 172.24.0.7:1234                                     
Remote debugging using 172.24.0.7:1234                                
0x00000000 in ?? ()                                                     
(gdb) info tra                                                        
No tracepoints.                                                       
(gdb) symbol-file /usr/local/bin/mybin1                             
Reading symbols from /usr/local/bin/ee/mybin1...done.                   
(gdb) info function  

<< list of functions from mybin1 >> 


(gdb) info tra                                                          
No tracepoints.                                                       
(gdb) tstart                                                          
(gdb)

I would like to know if this is an expected behavior for gdb?

Thanks in advance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

栖迟 2024-11-10 17:55:17

从 gdb 7.2 开始,行为是发出错误,而不是开始跟踪。

(gdb) tstart
No tracepoints defined, not starting trace
(gdb)

之前的行为是开始追踪但什么也没积累,
这似乎就是你所看到的。

http://sourceware.org/ml/gdb-patches/2010-03 /msg00918.html

since gdb 7.2 the behaviour has been to emit an error, and not start tracing.

(gdb) tstart
No tracepoints defined, not starting trace
(gdb)

The previous behaviour was to start tracing but accumulate nothing,
which seems to be what you are seeing.

http://sourceware.org/ml/gdb-patches/2010-03/msg00918.html

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文