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. Error during MSVC++ 6 Debug Mode

Error during MSVC++ 6 Debug Mode

Scheduled Pinned Locked Moved C / C++ / MFC
helpc++debuggingquestionannouncement
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.
  • R Offline
    R Offline
    romuzu
    wrote on last edited by
    #1

    Can anybody help me with this error? During debug mode I have receive this error message: MSVCRT.DLL: Access Violation. But if i Run my application on Release Mode. No error occured. Your help is appreciated.

    H M 2 Replies Last reply
    0
    • R romuzu

      Can anybody help me with this error? During debug mode I have receive this error message: MSVCRT.DLL: Access Violation. But if i Run my application on Release Mode. No error occured. Your help is appreciated.

      H Offline
      H Offline
      Hamid Taebi
      wrote on last edited by
      #2

      See msvcrt.dll access violation [^] maybe it is some helpful to you

      _**


      **_

      WhiteSky


      1 Reply Last reply
      0
      • R romuzu

        Can anybody help me with this error? During debug mode I have receive this error message: MSVCRT.DLL: Access Violation. But if i Run my application on Release Mode. No error occured. Your help is appreciated.

        M Offline
        M Offline
        Mike Dimmick
        wrote on last edited by
        #3

        The best approach is always to use the debugger. Run your program under the debugger (Build, Start Debug, Go). Do whatever you did to make the error occur. You'll get a dialog box reporting a 'First chance exception in MSVCRT.DLL (code 0xc0000005)'. Note the position of the instruction pointer. Look at the call stack window to see which part of your program called into the C runtime. You probably passed a NULL or invalid pointer into the C runtime somewhere. Most commonly this is due to an uninitialised variable: the debug version of the C runtime will initialise the stack to 0xCCCCCCCC, while the release version does not do this. The reason for doing this in debug mode is specifically to catch uses of bad pointers.

        Stability. What an interesting concept. -- Chris Maunder

        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