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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. User breakpoint called from code at 0x77f813b1

User breakpoint called from code at 0x77f813b1

Scheduled Pinned Locked Moved C / C++ / MFC
debugginghelptutorialquestionannouncement
18 Posts 7 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.
  • K KaRl

    Often this problem comes from memory which was corrupted somewhere in the application. So check in your code if you do not write outside an array, work with freed pointers, and so on.


    Jouir et faire jouir sans faire de mal ni à toi ni à personne, voilà je crois le fondement de toute morale Fold with us! ¤ flickr

    J Offline
    J Offline
    Jelahd
    wrote on last edited by
    #9

    You can debug from release mode if you build with program database and switch off the optimization. The debugger looks for the PDB file and will load it if present. Change project setting in C/C++ General Tab to disable(debug) optimization and create Debug Info in Program Database. Optimization can shuffle code around and remove redundant stuff which can confuse the debugger because the binary does not match the source. Good Luck.

    R 1 Reply Last reply
    0
    • J Jelahd

      You can debug from release mode if you build with program database and switch off the optimization. The debugger looks for the PDB file and will load it if present. Change project setting in C/C++ General Tab to disable(debug) optimization and create Debug Info in Program Database. Optimization can shuffle code around and remove redundant stuff which can confuse the debugger because the binary does not match the source. Good Luck.

      R Offline
      R Offline
      Rajasegar
      wrote on last edited by
      #10

      hi, thanx for the reply buddy.... This problem still persists in both the release and debug builds of the same program. Initially i tried to debug in release build, but now i tried it in debug build, and now also i am getting the same message, i have tried the settings you mentioned, but still the message appears....

      R@j@$eg@r

      T J J 3 Replies Last reply
      0
      • R Rajasegar

        hi, thanx for the reply buddy.... This problem still persists in both the release and debug builds of the same program. Initially i tried to debug in release build, but now i tried it in debug build, and now also i am getting the same message, i have tried the settings you mentioned, but still the message appears....

        R@j@$eg@r

        T Offline
        T Offline
        toxcct
        wrote on last edited by
        #11

        Read this[^]


        [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

        1 Reply Last reply
        0
        • R Rajasegar

          hi, thanx for the reply buddy.... This problem still persists in both the release and debug builds of the same program. Initially i tried to debug in release build, but now i tried it in debug build, and now also i am getting the same message, i have tried the settings you mentioned, but still the message appears....

          R@j@$eg@r

          J Offline
          J Offline
          jhwurmbach
          wrote on last edited by
          #12

          Rajasegar wrote:

          but now i tried it in debug build, and now also i am getting the same message

          Ok. The debugger should show you where in the code the error occures. Maybe you need to user the "Call Stack" window to step up the call stack to your code. There you should be able to find the problem.


          Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
          George Orwell, "Keep the Aspidistra Flying", Opening words

          1 Reply Last reply
          0
          • T toxcct

            [Message Deleted]

            M Offline
            M Offline
            Mark Salsbery
            wrote on last edited by
            #13

            toxcct wrote:

            you cannot debug a program compiled in release mode

            Hogwash ;P

            Mark Salsbery Microsoft MVP - Visual C++ :java:

            1 Reply Last reply
            0
            • R Rajasegar

              hi, thanx for the reply buddy.... This problem still persists in both the release and debug builds of the same program. Initially i tried to debug in release build, but now i tried it in debug build, and now also i am getting the same message, i have tried the settings you mentioned, but still the message appears....

              R@j@$eg@r

              J Offline
              J Offline
              Jelahd
              wrote on last edited by
              #14

              Should have said that the suggestion will only help you debug a release version of an app. Not necessarily find this specific problem. You could try the Exception dialog in the Debug menu. Only available during debugging. It lets you control debugger behaviour in the event of an exception. Can be useful but time consuming.

              1 Reply Last reply
              0
              • R Rajasegar

                I am trying to debug a program in release build. But after some time i getting a message like "User breakpoint called from code at 0x77f813b1" how to rectify this one? What actually is the problem here? Please help me.............

                R@j@$eg@r

                S Offline
                S Offline
                Stephen Hewitt
                wrote on last edited by
                #15

                Not enough information. Can you list the call stack? The OS version. A list of loaded DLL's and their versions and base addresses?

                Steve

                1 Reply Last reply
                0
                • T toxcct

                  [Message Deleted]

                  S Offline
                  S Offline
                  Stephen Hewitt
                  wrote on last edited by
                  #16

                  I come across this misconception all the time; there is no truth to it. There is nothing to stop you from enabling debug information for release builds. I do it all the time. The only issue is the MSVC IDEs don’t do this by default. If I made it they would.

                  Steve

                  T 1 Reply Last reply
                  0
                  • S Stephen Hewitt

                    I come across this misconception all the time; there is no truth to it. There is nothing to stop you from enabling debug information for release builds. I do it all the time. The only issue is the MSVC IDEs don’t do this by default. If I made it they would.

                    Steve

                    T Offline
                    T Offline
                    toxcct
                    wrote on last edited by
                    #17

                    we're talking about a user who don't even know the fundamental differences between debug and release... do you think he could have customized its settings by any chance ? :~


                    [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

                    S 1 Reply Last reply
                    0
                    • T toxcct

                      we're talking about a user who don't even know the fundamental differences between debug and release... do you think he could have customized its settings by any chance ? :~


                      [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

                      S Offline
                      S Offline
                      Stephen Hewitt
                      wrote on last edited by
                      #18

                      My response was to your assertion that, "you cannot debug a program compiled in release mode". This is simply not true.

                      Steve

                      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