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. Detect Debug Exes

Detect Debug Exes

Scheduled Pinned Locked Moved C / C++ / MFC
questionvisual-studiodebuggingcollaboration
3 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.
  • T Offline
    T Offline
    tojamismis
    wrote on last edited by
    #1

    Hey... Got a question about detecting debug vs. release configurations. I am working with an app at work that gave me an assertion error the other day. It included the filename and the line number in the error message. This would mean that the EXE we got from the vendor was compiled with DEBUG flags on. (I'm sort of a newbie (6 months as a convert from VB6).) My question is... is there any way to tell whether an exe or dll was compiled with Win32 Debug configuration without opening in a hex editor and looking for extra symbols? (I'm trying to see if I can automate the process for a software test team.) Thanks! Tojam

    P B 2 Replies Last reply
    0
    • T tojamismis

      Hey... Got a question about detecting debug vs. release configurations. I am working with an app at work that gave me an assertion error the other day. It included the filename and the line number in the error message. This would mean that the EXE we got from the vendor was compiled with DEBUG flags on. (I'm sort of a newbie (6 months as a convert from VB6).) My question is... is there any way to tell whether an exe or dll was compiled with Win32 Debug configuration without opening in a hex editor and looking for extra symbols? (I'm trying to see if I can automate the process for a software test team.) Thanks! Tojam

      P Offline
      P Offline
      Prakash Nadar
      wrote on last edited by
      #2

      one thing i would do is that open the exe or the dll with dependency walker and find anything that depends on debug dlls like mfc42d.dll or mfc42ud.dll if it does then this binary was build in debug version.

      1 Reply Last reply
      0
      • T tojamismis

        Hey... Got a question about detecting debug vs. release configurations. I am working with an app at work that gave me an assertion error the other day. It included the filename and the line number in the error message. This would mean that the EXE we got from the vendor was compiled with DEBUG flags on. (I'm sort of a newbie (6 months as a convert from VB6).) My question is... is there any way to tell whether an exe or dll was compiled with Win32 Debug configuration without opening in a hex editor and looking for extra symbols? (I'm trying to see if I can automate the process for a software test team.) Thanks! Tojam

        B Offline
        B Offline
        bilal78
        wrote on last edited by
        #3

        Well if you want, you can search on the net for Windows PE file Specification, and according to it ".exe" file compiled with debug information will have ".debug" section. If you find this section, this means your ".exe" file has dubug information included. Best Regards, Bilal Anjum

        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