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. how can i remove this error

how can i remove this error

Scheduled Pinned Locked Moved C / C++ / MFC
helpquestionc++performance
9 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.
  • P Offline
    P Offline
    pc_dev
    wrote on last edited by
    #1

    Given below is the error generated by vc6. It is related to memory leakage but the problem is that no file name/ line number is mentioned. how can i find/rectify the exact place of error? First-chance exception in TestApp.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception. Detected memory leaks! The thread 0x3C0 has exited with code 0 (0x0). The thread 0x3CC has exited with code 0 (0x0). Dumping objects -> The thread 0x660 has exited with code 0 (0x0). {56984} normal block at 0x078ECFE0, 4 bytes long. Data: < > 00 00 00 00 Object dump complete.

    C R V 3 Replies Last reply
    0
    • P pc_dev

      Given below is the error generated by vc6. It is related to memory leakage but the problem is that no file name/ line number is mentioned. how can i find/rectify the exact place of error? First-chance exception in TestApp.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception. Detected memory leaks! The thread 0x3C0 has exited with code 0 (0x0). The thread 0x3CC has exited with code 0 (0x0). Dumping objects -> The thread 0x660 has exited with code 0 (0x0). {56984} normal block at 0x078ECFE0, 4 bytes long. Data: < > 00 00 00 00 Object dump complete.

      C Offline
      C Offline
      Cedric Moonen
      wrote on last edited by
      #2

      By using your debugger. EDIT: maybe I misunderstood your question. The problem is only the memory leak, not the exception ? Because it seems you have an exception in your code, so it would be usefull to fix it.

      Cédric Moonen Software developer
      Charting control [v1.5] OpenGL game tutorial in C++

      modified on Thursday, September 4, 2008 10:40 AM

      R 1 Reply Last reply
      0
      • C Cedric Moonen

        By using your debugger. EDIT: maybe I misunderstood your question. The problem is only the memory leak, not the exception ? Because it seems you have an exception in your code, so it would be usefull to fix it.

        Cédric Moonen Software developer
        Charting control [v1.5] OpenGL game tutorial in C++

        modified on Thursday, September 4, 2008 10:40 AM

        R Offline
        R Offline
        Roger Stoltz
        wrote on last edited by
        #3

        Cedric Moonen wrote:

        By using your debugger.

        :laugh: A very technically correct answer that ought to be useless, but if it turns out to be useful it becomes priceless.

        "It's supposed to be hard, otherwise anybody could do it!" - selfquote
        "High speed never compensates for wrong direction!" - unknown

        C 1 Reply Last reply
        0
        • P pc_dev

          Given below is the error generated by vc6. It is related to memory leakage but the problem is that no file name/ line number is mentioned. how can i find/rectify the exact place of error? First-chance exception in TestApp.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception. Detected memory leaks! The thread 0x3C0 has exited with code 0 (0x0). The thread 0x3CC has exited with code 0 (0x0). Dumping objects -> The thread 0x660 has exited with code 0 (0x0). {56984} normal block at 0x078ECFE0, 4 bytes long. Data: < > 00 00 00 00 Object dump complete.

          R Offline
          R Offline
          Roger Stoltz
          wrote on last edited by
          #4

          Try the Visual Leak Detector[^] by Dan Moulding. It very useful and more accurate than I usually find VC6 to be.

          "It's supposed to be hard, otherwise anybody could do it!" - selfquote
          "High speed never compensates for wrong direction!" - unknown

          C 1 Reply Last reply
          0
          • R Roger Stoltz

            Cedric Moonen wrote:

            By using your debugger.

            :laugh: A very technically correct answer that ought to be useless, but if it turns out to be useful it becomes priceless.

            "It's supposed to be hard, otherwise anybody could do it!" - selfquote
            "High speed never compensates for wrong direction!" - unknown

            C Offline
            C Offline
            Cedric Moonen
            wrote on last edited by
            #5

            Well, seeing his question, I don't see how I can give a more accurate answer :rolleyes:

            Cédric Moonen Software developer
            Charting control [v1.5] OpenGL game tutorial in C++

            R 1 Reply Last reply
            0
            • R Roger Stoltz

              Try the Visual Leak Detector[^] by Dan Moulding. It very useful and more accurate than I usually find VC6 to be.

              "It's supposed to be hard, otherwise anybody could do it!" - selfquote
              "High speed never compensates for wrong direction!" - unknown

              C Offline
              C Offline
              Cedric Moonen
              wrote on last edited by
              #6

              As far as I understood, the exception is the problem (first line)...

              Cédric Moonen Software developer
              Charting control [v1.5] OpenGL game tutorial in C++

              R 1 Reply Last reply
              0
              • C Cedric Moonen

                Well, seeing his question, I don't see how I can give a more accurate answer :rolleyes:

                Cédric Moonen Software developer
                Charting control [v1.5] OpenGL game tutorial in C++

                R Offline
                R Offline
                Roger Stoltz
                wrote on last edited by
                #7

                Cedric Moonen wrote:

                Well, seeing his question, I don't see how I can give a more accurate answer

                Precisely, you're dead on, mate! You got my 5'er for providing the most accurate answer I've seen today. :cool:

                "It's supposed to be hard, otherwise anybody could do it!" - selfquote
                "High speed never compensates for wrong direction!" - unknown

                1 Reply Last reply
                0
                • C Cedric Moonen

                  As far as I understood, the exception is the problem (first line)...

                  Cédric Moonen Software developer
                  Charting control [v1.5] OpenGL game tutorial in C++

                  R Offline
                  R Offline
                  Roger Stoltz
                  wrote on last edited by
                  #8

                  Cedric Moonen wrote:

                  As far as I understood, the exception is the problem (first line)...

                  It is, but don't tell anyone. The experience you get from following the wrong track because you didn't read the debugger output is also priceless. :-\ First-hand exceptions rarely stops the execution, it just put an informative line in the debug output so I guess it's still about the memory leaks. But I've guessed wrong before... :-O

                  "It's supposed to be hard, otherwise anybody could do it!" - selfquote
                  "High speed never compensates for wrong direction!" - unknown

                  1 Reply Last reply
                  0
                  • P pc_dev

                    Given below is the error generated by vc6. It is related to memory leakage but the problem is that no file name/ line number is mentioned. how can i find/rectify the exact place of error? First-chance exception in TestApp.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception. Detected memory leaks! The thread 0x3C0 has exited with code 0 (0x0). The thread 0x3CC has exited with code 0 (0x0). Dumping objects -> The thread 0x660 has exited with code 0 (0x0). {56984} normal block at 0x078ECFE0, 4 bytes long. Data: < > 00 00 00 00 Object dump complete.

                    V Offline
                    V Offline
                    vikas amin
                    wrote on last edited by
                    #9

                    it can be step trough with the help of debugger , but it seems you have multiple threads , so you need to have breakpoints . also i recommand you to use try catch to avoid exceptions . Check your thread function , before they exit you are not deleting some memory allocated in the thread .

                    Vikas Amin

                    My First Article on CP" Virtual Serial Port "[^]

                    modified on Thursday, July 24, 2008 5:33 PM

                    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