Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. VS2017: Cannot debug Dll's

VS2017: Cannot debug Dll's

Scheduled Pinned Locked Moved C / C++ / MFC
debuggingannouncementcsharpc++visual-studio
4 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    indrekm
    wrote on last edited by
    #1

    I converted VS2008 solution (sln) to VS2017. Visual Studio is up-to-date - version 15.6.4. My solution contains tens of C++ projects - executables, dll's and lib's. Now I have a weird issue - dll's cannot be debugged in Debug configuration. In Release configuration it works - breakpoints can be used. But in Debug configuration all the breakpoints are disabled and there is a hint - "The breakpoint will not currently be hit. No symbols have been loaded for this document." When I try to load symbols (pdb) manually I'm getting a message "A matching symbol file was not found in this folder." In DLL project settings (vcxproj file) GenerateDebugInformation is true. I'm a bit confused why generated pdb file cannot be used by Visual Studio.

    L J 3 Replies Last reply
    0
    • I indrekm

      I converted VS2008 solution (sln) to VS2017. Visual Studio is up-to-date - version 15.6.4. My solution contains tens of C++ projects - executables, dll's and lib's. Now I have a weird issue - dll's cannot be debugged in Debug configuration. In Release configuration it works - breakpoints can be used. But in Debug configuration all the breakpoints are disabled and there is a hint - "The breakpoint will not currently be hit. No symbols have been loaded for this document." When I try to load symbols (pdb) manually I'm getting a message "A matching symbol file was not found in this folder." In DLL project settings (vcxproj file) GenerateDebugInformation is true. I'm a bit confused why generated pdb file cannot be used by Visual Studio.

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      The chances are that your DLL needs to be rebuilt.

      1 Reply Last reply
      0
      • I indrekm

        I converted VS2008 solution (sln) to VS2017. Visual Studio is up-to-date - version 15.6.4. My solution contains tens of C++ projects - executables, dll's and lib's. Now I have a weird issue - dll's cannot be debugged in Debug configuration. In Release configuration it works - breakpoints can be used. But in Debug configuration all the breakpoints are disabled and there is a hint - "The breakpoint will not currently be hit. No symbols have been loaded for this document." When I try to load symbols (pdb) manually I'm getting a message "A matching symbol file was not found in this folder." In DLL project settings (vcxproj file) GenerateDebugInformation is true. I'm a bit confused why generated pdb file cannot be used by Visual Studio.

        J Offline
        J Offline
        Jochen Arndt
        wrote on last edited by
        #3

        Have you converted the solution in-place (with existing output files from old VS 2008 builds)? Then try to delete all output files (especially old ones which can be identified by the time stamp).

        1 Reply Last reply
        0
        • I indrekm

          I converted VS2008 solution (sln) to VS2017. Visual Studio is up-to-date - version 15.6.4. My solution contains tens of C++ projects - executables, dll's and lib's. Now I have a weird issue - dll's cannot be debugged in Debug configuration. In Release configuration it works - breakpoints can be used. But in Debug configuration all the breakpoints are disabled and there is a hint - "The breakpoint will not currently be hit. No symbols have been loaded for this document." When I try to load symbols (pdb) manually I'm getting a message "A matching symbol file was not found in this folder." In DLL project settings (vcxproj file) GenerateDebugInformation is true. I'm a bit confused why generated pdb file cannot be used by Visual Studio.

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Hi, The 'Debug' build is just a text label... in other words it sounds like your DLL is being compiled with the symbols stripped out. There is nothing stopping someone from configuring 'Debug' exactly as a 'Release' build. Try using DUMPBIN /SYMBOLS[^] on your DLL to check if the symbol tables exists. Don't forget that you can PIPE the output into a text file:

          DUMPBIN /SYMBOLS YourDLL.DLL > symbols.txt

          Best Wishes, -David Delaune

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups