Thread: debug error: DAMAGE: after Normal block (#49) at 0x009F2C30

  1. #1
    Registered User
    Join Date
    Oct 2003
    Posts
    50

    debug error: DAMAGE: after Normal block (#49) at 0x009F2C30

    hi,

    i'm getting the debug assert in the subject line, but i'm not sure what it means.

    my best guess is that i have managed to overstep the bounds of one of my dynamic memory allocations, but if i have its not obvious and i don't want to spend hours looking for it if thats not the problem.

    (working in vc++6 on windows xp)

    thanks.

  2. #2
    Code Goddess Prelude's Avatar
    Join Date
    Sep 2001
    Posts
    9,897
    The memory manager for most implementations is very fragile. If you do anything wrong then it bombs with an obscure error like the one you got. The majority of my defensive programming is designed to maintain a high degree of locality between the source of the error and the error message. Otherwise you're stuck wading through tons of code.

    But your best guess is a good one. Try sprinkling your code with debug assertions to check boundaries.
    My best code is written with the delete key.

  3. #3
    Registered User
    Join Date
    Oct 2003
    Posts
    50
    Found it, was as i suspected.

    Thanks for your help.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. About aes
    By gumit in forum C Programming
    Replies: 13
    Last Post: 10-24-2006, 03:42 PM
  2. Replies: 12
    Last Post: 06-24-2005, 04:27 PM
  3. HUGE fps jump
    By DavidP in forum Game Programming
    Replies: 23
    Last Post: 07-01-2004, 10:36 AM
  4. Pointer's
    By xlordt in forum C Programming
    Replies: 13
    Last Post: 10-14-2003, 02:15 PM
  5. Manipulating the Windows Clipboard
    By Johno in forum Windows Programming
    Replies: 2
    Last Post: 10-01-2002, 09:37 AM