【问题标题】:Debugging PIN tool add-symbol-file doesn't work调试 PIN 工具 add-symbol-file 不起作用
【发布时间】:2015-11-18 16:07:56
【问题描述】:

要调试一个使用 PIN 工具的模拟器,通过使用 2 个不同的终端窗口,我执行以下操作:

/home/agy/mcsim/pin/intel64/bin/pinbin -pause_tool 5 -t /home/agy/mcsim/Pthread/mypthreadtool -port 47145 -skip_first 10000 -- McSim/JacNoBoost/JACCARD
Pausing to attach to pid 5465
To load the tool's debug info to gdb use:
   add-symbol-file /home/agy/mcsim/Pthread/mypthreadtool 0x7f86e6c06ee0 -s .data 0x7f86e709f620 -s .bss 0x7f86e70aaac0

在另一个窗口中,我执行以下操作:

gdb /home/agy/mcsim/Pthread/mypthreadtool
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/agy/mcsim/Pthread/mypthreadtool...done.
(gdb) attach 5465
Attaching to program: /home/agy/mcsim/Pthread/mypthreadtool, process 5465
0x0000000030592c70 in ?? ()
(gdb) add-symbol-file /home/agy/mcsim/Pthread/mypthreadtool 0x7f86e6c06ee0 -s .data 0x7f86e709f620 -s .bss 0x7f86e70aaac0
add symbol table from file "/home/agy/mcsim/Pthread/mypthreadtool" at
    .text_addr = 0x7f86e6c06ee0
    .data_addr = 0x7f86e709f620
    .bss_addr = 0x7f86e70aaac0
(y or n) y
Reading symbols from /home/agy/mcsim/Pthread/mypthreadtool...done.
(gdb) c
Continuing.

在某些时候,pin tool 冻结,我手动向 pin tool 发送中断信号并尝试在附加的窗口上对其进行调试。为了了解在哪一行 pin 实现卡住,我尝试了 backtrace 命令,但即使添加了符号文件,它也会返回问号。

Program received signal SIGINT, Interrupt.
0x000000003052c474 in ?? ()
(gdb) backtrace
#0  0x000000003052c474 in ?? ()
#1  0x00007f86e5570850 in ?? ()
#2  0x000000003070c290 in ?? ()
#3  0x0000000001dda880 in ?? ()
#4  0x0000000001dda880 in ?? ()
#5  0x000000000040e03a in ?? ()
#6  0x0000000030643de0 in ?? ()
#7  0x00007f86d5ada0c0 in ?? ()
#8  0x0000000000000012 in ?? ()
#9  0x00007f86e5571350 in ?? ()
#10 0x0000000030aade20 in ?? ()
#11 0x0000000000000000 in ?? ()

我在这里找不到错误的方法。你能帮帮我吗?

【问题讨论】:

  • Agy,你能确认你看到的地址在 pin 工具/pin 里面吗?执行cat /proc/&lt;pid&gt;/maps 并使用 pin 和 pintool 交叉引用这些地址范围。

标签: c++ gdb backtrace intel-pin


【解决方案1】:

我在这里找不到错误的方法。

您告诉 GDB mypthreadtool 是您的主要可执行文件,但它不是/home/agy/mcsim/pin/intel64/bin/pinbin 是。

试试这个:

gdb /home/agy/mcsim/pin/intel64/bin/pinbin 5465
(gdb) add-symbol-file /home/agy/mcsim/Pthread/mypthreadtool \
    0x7f86e6c06ee0 -s .data 0x7f86e709f620 -s .bss 0x7f86e70aaac0

【讨论】:

  • 用于 pin 调试的主要可执行文件是 pinbin。
  • @nitzanms 谢谢。已更新。
  • @nitzanms 和俄罗斯雇员感谢您的帮助。使用 pinbin 作为主要可执行文件并将 pid 替换为 5465 效果很好。
猜你喜欢
  • 1970-01-01
  • 2011-04-09
  • 2022-07-30
  • 1970-01-01
  • 2016-01-08
  • 2020-07-05
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多