MySQL C pdb 文件
我正在将 mysqlclient.lib 静态库用于我在 Visual Studio 2010 中制作的 C 项目。该程序构建得很好,但是当我尝试调试我的程序时,断点被挖空并显示“当前不会命中断点。尚未为此文档加载任何符号”。我已经包含了 mysqlclient.lib 的调试版本,但是在构建时我收到了一堆链接器警告。
mysqlclient.lib(sha.obj) : warning LNK4099: PDB 'taocrypt.pdb' was not found with
'mysqlclient.lib(sha.obj)' or at '/my project directory'\taocrypt.pdb'; linking
object as if no debug info
我收到每个 pdb 文件大约 7-8 个 obj 文件的警告。 未找到的 pdb 文件有 taocrypt.pdb、yassl.pdb、zlib.pdb、mysys.pdb、strings.pdb、dbug.pdb、clientlib.pdb
。我是否应该以某种方式将这些 pdb 文件包含在我的项目中? mysqlclient.lib 附带有一个 mysqlclient.pdb 文件,但我不知道如何处理它。我该怎么办?
干杯。
I'm using the mysqlclient.lib static library for a C project I am making in visual studio 2010. The program builds fine but when I try and debug my program the breakpoints are hollowed out and say "the breakpoint will not currently be hit. no symbols have been loaded for this document". I've included the debug version of the mysqlclient.lib however I get a bunch of linker warnings when building.
mysqlclient.lib(sha.obj) : warning LNK4099: PDB 'taocrypt.pdb' was not found with
'mysqlclient.lib(sha.obj)' or at '/my project directory'\taocrypt.pdb'; linking
object as if no debug info
And I get that warning for about 7-8 obj files per pdb file.
The pdb files that aren't found are taocrypt.pdb, yassl.pdb, zlib.pdb, mysys.pdb, strings.pdb, dbug.pdb, clientlib.pdb
. Am I supposed to include these pdb files in my project somehow? There's a mysqlclient.pdb file that comes with the mysqlclient.lib but I don't know what to do with it. What am I supposed to do with it?
Cheers.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
看看这个。
它说“在 Windows 上,mysqlclient.lib 中缺少 yaSSL 和 taocrypt 的符号,导致链接到该库的客户端出现未解决的符号错误。(Bug#27861)”
所以您可以尝试升级到更高版本的MySQL(5.0.48之后),看看是否出现问题。
Take a look at this.
It says "On Windows, symbols for yaSSL and taocrypt were missing from mysqlclient.lib, resulting in unresolved symbol errors for clients linked against that library. (Bug#27861)"
So you can try upgrading to a later version of MySQL (after 5.0.48) and see if the problem occurs.