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. Unhandled exception at 0x1b97d783 (mfc71d.dll) in graf.exe: User breakpoint.

Unhandled exception at 0x1b97d783 (mfc71d.dll) in graf.exe: User breakpoint.

Scheduled Pinned Locked Moved C / C++ / MFC
debugginghelpannouncement
6 Posts 4 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.
  • N Offline
    N Offline
    Neels
    wrote on last edited by
    #1

    this occurs while iam trying to use domodal() only in debug mode.. it works fine in release mode. help me to get rid of this...

    C I D 3 Replies Last reply
    0
    • N Neels

      this occurs while iam trying to use domodal() only in debug mode.. it works fine in release mode. help me to get rid of this...

      I Offline
      I Offline
      Iain Clarke Warrior Programmer
      wrote on last edited by
      #2

      If it happens in debug mode, then have you tried debugging it? Work backwards from the exception, and find out what wrong information you're giving to MFC? Iain.

      1 Reply Last reply
      0
      • N Neels

        this occurs while iam trying to use domodal() only in debug mode.. it works fine in release mode. help me to get rid of this...

        C Offline
        C Offline
        CPallini
        wrote on last edited by
        #3

        Maybe posting the code where exception happens will help. I can guess it is an ASSERT though. :)

        If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
        [my articles]

        N 1 Reply Last reply
        0
        • C CPallini

          Maybe posting the code where exception happens will help. I can guess it is an ASSERT though. :)

          If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
          [my articles]

          N Offline
          N Offline
          Neels
          wrote on last edited by
          #4

          Its in appcore.cpp // CWinApp diagnostics #ifdef _DEBUG void CWinApp::AssertValid() const { CWinThread::AssertValid(); ASSERT(afxCurrentWinApp == this); ASSERT(afxCurrentInstanceHandle == m_hInstance); if (AfxGetThread() != (CWinThread*)this) return; // only do subset if called from different thread if (m_pDocManager != NULL) ASSERT_VALID(m_pDocManager); }

          C 1 Reply Last reply
          0
          • N Neels

            Its in appcore.cpp // CWinApp diagnostics #ifdef _DEBUG void CWinApp::AssertValid() const { CWinThread::AssertValid(); ASSERT(afxCurrentWinApp == this); ASSERT(afxCurrentInstanceHandle == m_hInstance); if (AfxGetThread() != (CWinThread*)this) return; // only do subset if called from different thread if (m_pDocManager != NULL) ASSERT_VALID(m_pDocManager); }

            C Offline
            C Offline
            CPallini
            wrote on last edited by
            #5

            As you can see, you don't get an exception on release version, because the code is inside _DEBUG guard (BTW ASSERT itsef is guarded by _DEBUG). Anyway it seems your application's m_Instance has not the proper value, maybe you have to check its value with the debugger. :)

            If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
            [my articles]

            1 Reply Last reply
            0
            • N Neels

              this occurs while iam trying to use domodal() only in debug mode.. it works fine in release mode. help me to get rid of this...

              D Offline
              D Offline
              David Crow
              wrote on last edited by
              #6

              Neels wrote:

              it works fine in release mode.

              No, it only APPEARS to work. The problem exists in both, but because of the differences in the way each is compiled, variables are initialized, etc, the problem has simply been moved or masked.

              "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman

              "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

              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