![cannot set breakpoint in visual studio 2017 remote debugger cannot set breakpoint in visual studio 2017 remote debugger](https://i.stack.imgur.com/Lc4YI.png)
I notice that the symbol file is generated in all lower case, even though my app has upper case charaters in the name. Well, it was generated at the same time the module was by the same execution of the compiler/linker, so I am not sure how it does not match. I get a message back saying that the symbol file. So in the "modules" window in the debugger I right click on the DLL where my breakpoint is located and click "Load Symbols" and specify the.
![cannot set breakpoint in visual studio 2017 remote debugger cannot set breakpoint in visual studio 2017 remote debugger](https://i.ytimg.com/vi/S7Jcur8YAsw/maxresdefault.jpg)
pdb files at every step, and I have specified the symbol file path(s) to point to these files. And what exactly is the point of having every project create something called "VC80.pdb" rather than defaulting to the project name or output file name? A mystery! In any case, I did all that. Apparently this is not a default setting, even when /DEBUG is specified. I had to go back and modify a number of properties settings to get VS2005 to create. Leave files in their default locations and you might have less trouble? (I know you already checked, check again.) Delete any old versions of your app or DLLs. Check the paths for files in the Modules window (Debug->Windows->Modules) and make sure your files are where you expect. functionality of VS would work correctly to locate the PDB file. When I deleted the old version of the DLL then I could move the new version wherever I wanted to and the Symbol Settings. When my DLL was not in the same directory as the PDB file the application would load an old version of the DLL from C:/Windows/System32 instead of the new version that I just built? I didn't think there was a copy in System32 because I got an error message when I had tried to register the DLL way back when. In the Modules window in the debugger it actually shows the path name of the module in addition to the file name. As I tried deleting my DLL file and moving it around to different locations I noticed something for the first time. pdb file so I did some more testing to try to figure out what was really going on. I had also played around with the upper case/lower case thing with the app name and. Debug/ and my breakpoints showed up like they were supposed to!!!Īs happy as I was that I could now hit breakpoints I still had the feeling that something was not right. Thinking that this might be part of the problem I moved the output back to the default location of. In my project I had the output DLL generated in a different directory than the normal. GAAAAAA! (That is my Dilbert immitation.) Is this not supposed to work any more in the new version of VS? None of the ideas mentioned in other postings seem to help for my problem.
Cannot set breakpoint in visual studio 2017 remote debugger code#
I have added the paths to the dll and lib source code and debug build folders (PDB files) to the "Symbol Settings." for the VB exe. The dll and lib do not show up in the modules list. What I need to do is load the symbols for my C++ code. I see the VB executable in the modules window, and it shows that the symbols for it have been loaded. I have read lots of postings regarding this and still am in a fog.ĭo all of these differenct projects (VB, C++ dll, C++ lib) need to be part of the same solution in order for this to work? In my case they are separate solutions (as they were in VS 6.0). Now when it do this my C++ breakpoints show up with the note that they cannot be hit because the symbols are not loaded. In VS 6.0 I used to run the VB exe program and then use Attach to Process. These were all originally developed in MSVS 6.0 and have been ported over to VS 2005 (i.e.