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. Debugging application minidump using windbg

Debugging application minidump using windbg

Scheduled Pinned Locked Moved C / C++ / MFC
c++dotnetdebuggingquestion
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.
  • P Offline
    P Offline
    Prasann Mayekar
    wrote on last edited by
    #1

    i have an MFC c++ application build with /clr option and have integrated crash reporting feature. the crash dump it generates does not show line numbers when i debug the dump using windbg. (i found that applications build with clr does not show line numbers) it shows the function name where it crashed but not the exact line number. for eg it shows: 03434456 02312434 CExApp::OnOpenFile() + 0x30c whats 0x30c ? is it an offset in the function? Is there any way to calculate the line number by using 0x30c ? thanks

    S 1 Reply Last reply
    0
    • P Prasann Mayekar

      i have an MFC c++ application build with /clr option and have integrated crash reporting feature. the crash dump it generates does not show line numbers when i debug the dump using windbg. (i found that applications build with clr does not show line numbers) it shows the function name where it crashed but not the exact line number. for eg it shows: 03434456 02312434 CExApp::OnOpenFile() + 0x30c whats 0x30c ? is it an offset in the function? Is there any way to calculate the line number by using 0x30c ? thanks

      S Offline
      S Offline
      Sarath C
      wrote on last edited by
      #2

      See if your PDBs, Source file and image (exe) matches. I am not sure SOS DLL can help you with Postmortem debugging. But have a look at it[^]

      -Sarath.

      My blog - Reflections of my thoughts

      Rate the answers and close your posts if it's answered

      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