Valgrind 丢失符号信息
运行 Valgrind 后，生成的日志文件包含许多错误，看起来像
Conditional jump or move depends on uninitialised value(s)
at 0x3D9863AA: ???
by 0x3D986287: ???
by 0x3D9854AC: ???
Uninitialised value was created by a heap allocation
at 0x7FCC050: operator new(unsigned int) (vg_replace_malloc.c:214)
by 0x3D9A56A4: ???
by 0x3D9A4EB9: ???
在环顾四周后，我发现了以下行，我认为这对于获取实际内容很重要，而不仅仅是 ???：
Discarding syms at 0x3d97dba0-0x3da53de8 in /path/SomeDLL.so due to munmap()
请注意，所有??? 来自 Discarding syms 行指定范围内的地址。
是什么导致 Valgrind 丢弃共享库的符号信息以及如何修复它？
After running Valgrind, the resultant log file contains a number of errors that look like
Conditional jump or move depends on uninitialised value(s)
at 0x3D9863AA: ???
by 0x3D986287: ???
by 0x3D9854AC: ???
Uninitialised value was created by a heap allocation
at 0x7FCC050: operator new(unsigned int) (vg_replace_malloc.c:214)
by 0x3D9A56A4: ???
by 0x3D9A4EB9: ???
After looking around I found the following line which I think is important to getting actual content instead of just ???:
Discarding syms at 0x3d97dba0-0x3da53de8 in /path/SomeDLL.so due to munmap()
Note that all ??? come from addresses in the ranges specified by Discarding syms lines.
What is causing Valgrind to throw away symbol information for shared libraries and how do I fix it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
也许您的共享库已被 dlclose 调用卸载。尽量避免这种情况。请参阅 Valgrind 常见问题解答
Maybe your shared library was unloaded by
dlclosecall. Try to avoid this. See Valgrind FAQ