blocks|key|2314910|text|我遇到的问题之一是，在代码所在的引用项目上，调试是关闭的。在我的例子中，我做了一个名为"Developer“的新配置，默认情况下，调试被关闭。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2314911|右击所讨论的项目|ordered-list-item|2314912|属性|2314913|构建|2314914|高级(右下角)|2314915|将Debug信息设置为完整|2314916|重新编译|2314917|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

One of the things I've ran into with was because debug was off on the project referenced where the code lives. In my case, I made a new configuration called "Developer" and by default debug was turned off.

<ol>
<li>Right click the project in question</li>
<li>Properties</li>
<li>Build</li>
<li>Advanced (right bottom corner)</li>
<li>Set Debug Info to full</li>
<li>Recompile</li>
</ol>

blocks|key|2673859|text|我和@DmainEvent有同样的问题。显然，我使用的dll与我刚才编译的pdb不同，所以我得到了错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2673860|如果有此问题，请尝试使用同一编译运行中的dll和pdb。|2673861|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem as @DmainEvent. Apparently the dll that I was using was not the same version as the pdb that I had just compiled, so I got the error message.

If you have this problem, try using the dll and pdb from the same compilation run.

blocks|key|2674010|text|我得到的错误是“在Debug+=>模块窗口中找不到匹配的符号文件”，即使DLL和PDB都可用并一起构建，所以我无法调试到主项目引用的目标DLL中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2674011|张贴在这里，以防它帮助某人浏览与“混合平台”为目标DLL构建。我做了两件事来克服这一切：|2674012|在使用目标DLL的解决方案中，在Tools+=>+Options+=>+Debugging+=>+General+=>中取消选中“JMC”，只启用My+(JMC)。|ordered-list-item|2674013|检查相关项目属性=>调试中目标DLL解决方案中的“启用本机代码调试”。|2674014|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

The error I got was "a matching symbol file was not found in this folder" in the Debug => Modules window even after both the DLL and PDB were available and built together, so I was unable to debug into the target DLL referenced by my main project.

Posting this here in case it helps someone browsing with "Mixed Platform" build for target DLL. I did two things to get past this:

<ol>
<li>In the solution using the target DLL, Uncheck "Just My Code" in Tools => Options => Debugging => General => Enable Just My Code (JMC).</li>
<li>Check "Enable native code debugging" in target DLL solution in relevant Project Properties => Debug.</li>
</ol>

blocks|key|1117966|text|我尝试了所有可能的解决方案，当我在Debugger+engines+of+Properties+>+Debug下禁用选项Properties+>+Debug时，它终于起了作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1117967|entityMap^0|H|G|11|I|1O|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I tried all the possible solutions, finally it worked when I disabled the option <code>Enable native code debugging</code> under the <code>Debugger engines</code> of <code>Properties &gt; Debug</code>.

blocks|key|2314965|text|我遇到了这个问题，答案很简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2314966|Visual有两个可以创建.pdb文件的项目级别设置。|2314967|链接器:配置属性->链接器->调试->生成程序数据库文件=+"xxxx.pdb“|ordered-list-item|2314968|编译器:配置属性->+C/C%2B%2B+->输出文件->程序数据库文件名=+"yyyy.pdb“|2314969|您希望#1用于调试。忘记#2，给文件#2取一个与文件#1不同的名称来解决这个错误。|2314970|我不知道为什么微软将#2指定为.pdb文件。这太让人困惑了。|2314971|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

I ran into this problem and the answer was simple.

Visual studio has two project level settings that can create .pdb files.

<ol>
<li>Linker: Configuration Properties -> Linker -> Debugging -> Generate
 Program Database File = "xxxx.pdb" </li>
<li>Compiler: Configuration Properties -> C/C++ -> Output Files -> Program Database File Name =
"yyyy.pdb"</li>
</ol>

You want #1 for debugging. Forget about #2. 
Give file #2 a different name than file #1 to solve this error.

I don't know why microsoft specifies #2 as a .pdb file. That is just confusing.

blocks|key|1118117|text|我已经修复了我的调试符号，迫使它们使用以下工具进行匹配：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118118|chkmatch工具|offset|length|1118119|编辑:网站现在关闭了。回程机的帮助：https://web.archive.org/web/20210205095232/https://www.debuginfo.com/tools/chkmatch.html|1118120|因此，我的问题是，我试图调试我的项目，而调试器无法进入内部的nuget源代码。我有nuget项目的源文件。尽管如此，仍然不接受我试图展示给它的pdb文件。显示完全相同的错误：|1118121|在此文件夹中找不到匹配的符号文件。|blockquote|1118122|因此，我所做的就是将它添加到nuget项目的.proj文件中：|1118123|<DebugType>full</DebugType>|code-block|syntax|javascript|1118124|并再次使用重构选项创建dll和pdb文件。在命令行中，我运行了：|1118125|.\ChkMatch.exe+-m+name_of_your.dll+name_of_your.pdb++++|1118126|它说：|1118127|写入调试信息文件..。结果:成功。|1118128|伟大的成功！因此，接下来，我将这个dll引用到我试图调试的proj。我工作时，我试图再次加载符号。|1118129|希望能帮上忙。|1118130|entityMap|0|LINK|mutability|MUTABLE|url|http://www.debuginfo.com/tools/chkmatch.html|1|https://web.archive.org/web/20210205095232/https://www.debuginfo.com/tools/chkmatch.html^0|0|0|A|0|0|I|2G|1|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1G|8|@]|9|@$D|1H|E|1I|1|1J]]|A|$]]|$1|F|3|G|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]]|A|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1R|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|1S|8|@]|9|@]|A|$]]|$1|V|3|W|5|Q|7|1T|8|@]|9|@]|A|$R|S]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|10|5|L|7|1V|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1W|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1X|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|18|19|1A|A|$1B|1E]]]]

I have fixed my debug symbols, forcing them to match using this tool:
<a href="http://www.debuginfo.com/tools/chkmatch.html" rel="nofollow noreferrer">chkmatch tool</a>
edit: the website is down now. the wayback machine helps: <a href="https://web.archive.org/web/20210205095232/https://www.debuginfo.com/tools/chkmatch.html" rel="nofollow noreferrer">https://web.archive.org/web/20210205095232/https://www.debuginfo.com/tools/chkmatch.html</a>
So, my problem was I was trying to debug my project and the debugger couldn't step-in to the in-house nugets sources. I had the source files of the nuget project. Still the visual studio didn't accept the pdb files I was trying to show it to.
Showing exact same error:
<blockquote>
a matching symbol file was not found in this folder
</blockquote>
So, what I did was I added this to the .proj file of the nugets project:
<pre><code>&lt;DebugType&gt;full&lt;/DebugType&gt;
</code></pre>
And created the dll and pdb file again using the rebuild option.
In the command line I ran:
<pre><code>.\ChkMatch.exe -m name_of_your.dll name_of_your.pdb 
</code></pre>
It said this:
<blockquote>
Writing to the debug information file...
Result: Success.
</blockquote>
Great success!
So, next, I referenced this dll instead to the proj I was trying to debug. I worked when I tried to load the symbol again.
Hope it helps.

blocks|key|2314892|text|如果没有更多关于您正在做什么的详细信息，就很难超越“调试器正在寻找一个与已编译代码匹配的符号文件，并且在编译代码所在的文件夹中找不到一个。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2314893|有些事情需要考虑：|2314894|您是否正在创建符号作为编译的一部分？(检查项目属性)|ordered-list-item|2314895|您是否使用符号服务器(如果使用，它是否指向正确的位置)|2314896|这是来自第三方的编译代码吗？在这种情况下，显然您有源代码，自己编译它。|2314897|如果你想得到更好的答案，可以考虑澄清你的问题。尤其是你所说的“我要使用符号”是什么意思。|2314898|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

Without more details as to what you're doing, it's difficult to go beyond "the debugger is looking for a symbol file which matches the compiled code, and couldn't find one in the folder where the compiled code lives."

Some things to think about:

<ol>
<li>Are you creating symbols as part of your compilation? (check the project properties)</li>
<li>Are you using a symbol server (if so, does it point to the right place)</li>
<li>Is this compiled code from a third party? In which case, as you apparently have the source, compile it yourself.</li>
</ol>

Consider clarifying your question if you want a better answer. Especially what do you mean by "I want use of Symbols".

blocks|key|2315111|text|对于BizTalk+(和其他)项目，这可能是因为在GAC中已经有您要调试的程序集的版本。当您运行单元测试或按F5进行调试时，新版本将在本地编译。但是，正在使用GAC中的版本，新创建的PDB与GAC中的DLL不匹配。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2315112|解决这一问题的一种方法是取消使用Configuration为所有内容(单元测试项目除外)选择构建，如下所示：|2315113|​|2315114|📷|atomic|offset|length|2315115|2315116|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/fe6e8482792b115a4ad121e8b52b592e.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

For BizTalk (and other) projects, it could be because there's a version of the assembly you're trying to debug already in the GAC. When you run a unit test or hit F5 to debug, a new version is compiled locally. However, the version in the GAC is being used, and the newly created PDB doesn't match the DLL in the GAC.

One way around this is to deselect a build for everything except your unit test project using the Configuration Manager, as shown below:

<a href="https://i.stack.imgur.com/V5yvS.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/V5yvS.png" alt="Config Manager"></a>

blocks|key|2315152|text|解决办法取决于你的具体问题。我尝试了所有可能在Stackoverflow和其他网站上找到的东西。我关注的一个线程是这。这也于事无补。当我注意到我的可执行项目没有包含对我想要调试的库的引用时，这个问题就解决了。所以我只是添加了那个项目的参考资料。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2315153|**PS：**此问题也可能出现，因为可执行程序集引用的程序集可能与引用中的程序集不匹配。因此，在这种情况下，您只需删除已经存在的引用并添加新的引用。|2315154|希望这能有所帮助！|2315155|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2155930/how-do-i-remedy-the-the-breakpoint-will-not-currently-be-hit-no-symbols-have-b?page=3&tab=votes#tab-top^0|21|3|2H|1|1L|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Well, the solution depends on your specific problem. I tried everything that could be possibly found on Stackoverflow and other sites. One of the thread that I followed is <a href="https://stackoverflow.com/questions/2155930/how-do-i-remedy-the-the-breakpoint-will-not-currently-be-hit-no-symbols-have-b?page=3&amp;tab=votes#tab-top">this</a>. That did not help too.
The problem was at once resolved when I noticed that my executable project did not contain a reference to the library that I wanted to debug. So I just added the reference to that project.

**PS: ** This problem might also arise because the assembly referenced by the executable assembly might not match that in the references. So in that case, you just remove the already existing reference and add the new one.

Hope this helps!

blocks|key|2674031|text|同样的情况也发生在我身上，因为项目的.pdb文件尚未复制到debug\Bin文件夹中，因此无法从.pdb文件中加载符号。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2674032|必须重新生成项目，并手动将符号(.pdb文件)复制到可执行项目的debug\Bin文件夹中。|2674033|entityMap^0|T|9|0|W|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

The same happen to me because the .pdb file of the project have not been copied to the <code>debug\Bin</code> folder, so the symbols could not be loaded from the .pdb file.

You must rebuild your project and manually copy the symbols (.pdb file) to the <code>debug\Bin</code> folder of executable project.

blocks|key|2674094|text|我试图为本地dev服务器上发布的已安装的nuget包加载符号。我不得不卸载并添加一个从代码构建的正常引用。这对我有用。只需记住，一旦调试完成，请再次安装原始nuget包。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2674095|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was trying to load symbols for a installed nuget package published on our local dev server. I had to uninstall and add a normal reference built from the code instead. This worked for me. Just remember install the original nuget package again once finished debugging.

blocks|key|1118143|text|如果它对您有效，请尝试将调试符号嵌入dll本身，以便自动加载符号。在netcoreapp3.1和net5.0中，这对我起了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118144|<DebugType>Embedded</DebugType>
<EmbedAllSources>True</EmbedAllSources>|code-block|syntax|javascript|1118145|请注意，您可能会在文档中找到这一点：|1118146|<AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>|1118147|但不起作用。|1118148|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If it works for you, try to embed debug symbols in the dll itself, so the symbols are loaded automatically. This worked for me in netcoreapp3.1 and net5.0:
<pre><code>&lt;DebugType&gt;Embedded&lt;/DebugType&gt;
&lt;EmbedAllSources&gt;True&lt;/EmbedAllSources&gt;
</code></pre>
Beware that you may find this in documentation:
<pre><code>&lt;AllowedOutputExtensionsInPackageBuildOutputFolder&gt;$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb&lt;/AllowedOutputExtensionsInPackageBuildOutputFolder&gt;
</code></pre>
but it does not work.

blocks|key|1118181|text|我在Visual+2022中遇到了这个问题，在这里尝试了大部分答案。通过切换回VisualStudio2019进行修复，在2022年似乎是一个bug。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118182|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I ran into this with Visual Studio 2022, tried the most of answers here. Fixed by switching back to Visual Studio 2019, seems like a bug in 2022.

blocks|key|1117920|text|我发现这是因为Properties+=>+Debug+=>+Start+Action被设置为启动外部程序，而不是项目。所以新生成的pdb文件不匹配，因为实际的exe是错误的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1117921|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I found this was because the Properties => Debug => Start Action was set to Start external program instead of the Project. So the newly generated pdb file didn't match, because the actual exe was the wrong one.

blocks|key|2315006|text|最近我也遇到了这个问题。通过选择MyProject->Properties->Linker->Debugging->Generate+debugging+>“优化调试(/DEBUG)”可以修复它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2315007|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have had this problem recently as well. 
Was able to fix it by selecting MyProject->Properties->Linker->Debugging->Generate Debug Info->"Optimize for debugging (/DEBUG)".

I want to use debug symbols, but I am receiving the following error: 

<blockquote>
 a matching symbol file was not found in this folder
</blockquote>

What is this problem, and how to solve it?

a matching symbol file was not found in this folder

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想使用调试符号，但是我收到了以下错误：在此文件夹中找不到匹配的符号文件。这个问题是什么，如何解决？

问在此文件夹中找不到匹配的符号文件。
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在此文件夹中找不到匹配的符号文件。EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在此文件夹中找不到匹配的符号文件。
EN