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. Debug VS2005 application

Debug VS2005 application

Scheduled Pinned Locked Moved C / C++ / MFC
helpdebuggingquestion
4 Posts 3 Posters 1 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.
  • D Offline
    D Offline
    DanYELL
    wrote on last edited by
    #1

    I have VS6, which is a great little compiler. If I had an error, VS6 showed me the error and what lead up to the error. That is, what functions where called before the error. That helped me spot where the error was. Im using VS2005 and when an error arises, I just see the error. Is there a way finding out what functions were called just before that error was committed? Please let me know because that will be help me debug an application Im working on. Sincerely, Danielle Brina

    C 1 Reply Last reply
    0
    • D DanYELL

      I have VS6, which is a great little compiler. If I had an error, VS6 showed me the error and what lead up to the error. That is, what functions where called before the error. That helped me spot where the error was. Im using VS2005 and when an error arises, I just see the error. Is there a way finding out what functions were called just before that error was committed? Please let me know because that will be help me debug an application Im working on. Sincerely, Danielle Brina

      C Offline
      C Offline
      Chris Losinger
      wrote on last edited by
      #2

      when your app stops, go to the Debug menu, in the Windows sub-menu, find "Call Stack".

      image processing toolkits | batch image processing

      D A 2 Replies Last reply
      0
      • C Chris Losinger

        when your app stops, go to the Debug menu, in the Windows sub-menu, find "Call Stack".

        image processing toolkits | batch image processing

        D Offline
        D Offline
        DanYELL
        wrote on last edited by
        #3

        Thank you. That worked.

        1 Reply Last reply
        0
        • C Chris Losinger

          when your app stops, go to the Debug menu, in the Windows sub-menu, find "Call Stack".

          image processing toolkits | batch image processing

          A Offline
          A Offline
          Albert Holguin
          wrote on last edited by
          #4

          Call stack is a great tool for this... :thumbsup:

          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