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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Using pdb file

Using pdb file

Scheduled Pinned Locked Moved C / C++ / MFC
announcementc++debuggingsaleshelp
2 Posts 2 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.
  • V Offline
    V Offline
    VVVimal
    wrote on last edited by
    #1

    Hi All I am using MFC SDI application. We give release version of executable to the customer. Application get's crahses in real time. I heard through pdb file we can debug the release version. Can any one tell how to use the pdb file. In real time we cannot debug the executable via code. Also it occurs in rare case. Finding the solution is bit difficult. Can anyone assist me in resolving this issue.

    N 1 Reply Last reply
    0
    • V VVVimal

      Hi All I am using MFC SDI application. We give release version of executable to the customer. Application get's crahses in real time. I heard through pdb file we can debug the release version. Can any one tell how to use the pdb file. In real time we cannot debug the executable via code. Also it occurs in rare case. Finding the solution is bit difficult. Can anyone assist me in resolving this issue.

      N Offline
      N Offline
      Niklas L
      wrote on last edited by
      #2

      I have not used it to actually debug an application at runtime, but rather used it when analyzing crash dumps from release builds, but I suppose that is possible too. The pdb file contains the symbol information needed to trace instructions back to source code. If the problem occurs infrequently, it might be better to go the crash dump analysis path. There is a discussion here[^] on how to do this.

      home

      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