重新设置断点时出现GDB错误(无法访问内存)
gdb error in re-settings breakpoint (cannot access memory)
我试图让gdb在pcbsd10 (freebsd10)中设置一个断点。
我已经用调试符号编译了我的代码,下面是gdb 的输出GNU gdb (GDB) 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-unknown-freebsd10.0".
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 tor...done.
(gdb) break config.c:3626
Breakpoint 1 at 0xfde72: file src/or/config.c, line 3626.
(gdb) run
Starting program: /usr/home/jon/swdev/apps/tor/src/or/tor -f /home/jon/torrc
Error in re-setting breakpoint 1: Cannot access memory at address 0xfdb90
Error in re-setting breakpoint 1: Cannot access memory at address 0xfdb90
...
并且我的代码继续运行而不会在断点处停止。
这是怎么回事?如何更深入地了解gdb失败的原因?
您可能正在查看这个GDB错误。
虽然看起来GDB 7.7应该已经修复了,但您可能想要尝试7.7.1。
或者,将二进制文件构建为非pie二进制(从Makefile中删除-fPIE
)。
相关文章:
- gdb错误:Backtrace已停止:上一帧与此帧相同(堆栈已损坏?)
- 这是 ubuntu 16.04 中的 gdb 错误吗?
- cuda-gdb 给出错误"warning: Cuda API error detected: cudaLaunchKernel returned (0x7)"
- GDB 共享库中的文件名错误
- 如何解释GDB回溯以确定分段错误?
- GDB 列表错误"No such file or directory"
- 段错误,但不是在瓦尔格林德或GDB中
- GDB错误不以可执行格式:未识别的文件格式
- 使用GDB修复大型项目中的双自由或损坏(!prev)错误
- GDB无法加载,因此文件和错误没有此类文件或目录
- 有什么方法可以修复 CLion 中使用 SFML 的程序"command timed out" GDB 错误?
- GDB 错误"cp_search_static_and_baseclasses"
- GDB算术异常 - 无零分割 - 运行时错误
- 使用 GDB 在 main() 之前调试错误
- GDB以无序的方式跳转到错误的行
- vector.size()的GDB值错误
- 如果在例程中,Gdb 会在错误时中断
- GDB 7.11启动错误
- Valgrind+gdb用MPI调试,库中有错误
- 代码精简版调试器错误:无法找到 gdb!在'/usr/bin/gdb'