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. Other Discussions
  3. The Soapbox
  4. Visual C++/MFC and ASSERT...

Visual C++/MFC and ASSERT...

Scheduled Pinned Locked Moved The Soapbox
c++visual-studiocsharpdebuggingjson
3 Posts 2 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.
  • J Offline
    J Offline
    Jorgen Sigvardsson
    wrote on last edited by
    #1

    Once an MFC application is terminating, weird stuff is happening. If an ASSERT fires once ExitInstance() is called, the process is terminated, by means of some structured exception I suppose - haven't researched it yet, skipping the rest of my ExitInstance() method. This results in a MASSIVE memory leak report by the debug CRT, which messes with Visual Studio (it takes ages for the IDE to pump all the text out to the output pane). GAH...!

    -- Kein Mitleid Für Die Mehrheit

    S 1 Reply Last reply
    0
    • J Jorgen Sigvardsson

      Once an MFC application is terminating, weird stuff is happening. If an ASSERT fires once ExitInstance() is called, the process is terminated, by means of some structured exception I suppose - haven't researched it yet, skipping the rest of my ExitInstance() method. This results in a MASSIVE memory leak report by the debug CRT, which messes with Visual Studio (it takes ages for the IDE to pump all the text out to the output pane). GAH...!

      -- Kein Mitleid Für Die Mehrheit

      S Offline
      S Offline
      Single Step Debugger
      wrote on last edited by
      #2

      Are you sure you don’t have a method call inside some like: ASSERT(ImCrasy())? :-D

      The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.

      J 1 Reply Last reply
      0
      • S Single Step Debugger

        Are you sure you don’t have a method call inside some like: ASSERT(ImCrasy())? :-D

        The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.

        J Offline
        J Offline
        Jorgen Sigvardsson
        wrote on last edited by
        #3

        ASSERT(!"WTF?"); is the offender in question. :-D I have it there to mark a situation that should never arise. It happened because I was working at home, and the database wasn't up to par with the current development database. :)

        -- Kein Mitleid Für Die Mehrheit

        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