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. A Bug in Release version of VC++

A Bug in Release version of VC++

Scheduled Pinned Locked Moved C / C++ / MFC
helpannouncementc++performance
4 Posts 3 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
    jossion
    wrote on last edited by
    #1

    I am having a video decoder application for which I prepared a Release version. The program crashes with a message "The instruction at 0x77fc8e1 referenced to a memory 0x0000001 which could not be written. I inserted AfxMessageBox() at different points and finally found the bug pointing to a memory freeing portion. But if I remove one AfxMessageBox() the error code changes(0x0000001 becomes 0xfffffff). If I reposition the code then error occurs for some other memory freeing block. Has anyone come across such a behaviour. If so I need valuable suggestions.

    C 1 Reply Last reply
    0
    • J jossion

      I am having a video decoder application for which I prepared a Release version. The program crashes with a message "The instruction at 0x77fc8e1 referenced to a memory 0x0000001 which could not be written. I inserted AfxMessageBox() at different points and finally found the bug pointing to a memory freeing portion. But if I remove one AfxMessageBox() the error code changes(0x0000001 becomes 0xfffffff). If I reposition the code then error occurs for some other memory freeing block. Has anyone come across such a behaviour. If so I need valuable suggestions.

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

      This article[^] could be helpfull.


      Cédric Moonen Software developer
      Charting control [v1.2 - Updated]

      J 1 Reply Last reply
      0
      • C Cedric Moonen

        This article[^] could be helpfull.


        Cédric Moonen Software developer
        Charting control [v1.2 - Updated]

        J Offline
        J Offline
        jossion
        wrote on last edited by
        #3

        I have gone through this article. The only possibilit that may occur for me is uninitialized local variables and bound errors. I have done with those except for a small doubt. How to initialize pointers such as int *temp_array and int **double_array.

        J 1 Reply Last reply
        0
        • J jossion

          I have gone through this article. The only possibilit that may occur for me is uninitialized local variables and bound errors. I have done with those except for a small doubt. How to initialize pointers such as int *temp_array and int **double_array.

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

          jossion wrote:

          How to initialize pointers such as int *temp_array and int **double_array

          int *temp_array pTemparray = NULL; int **double_array pDoublearray = NULL;


          Failure is not an option - it's built right in.

          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