It definitely means something is writing data where it should not be (array
overrun, assigning vales to an object that has already been deleted, etc. ).
This is a message from the runtime memory allocation functions that tells
you something overwrote memory where it should not have. The damage is
detected by the functions checking the fill values that are placed in the
extra 'dead zones' put around each allocated block.
Use the MSDN cd (or on the MS web site) to get info about afxMemDF (for MFC
allocation) and _CrtSetDbgFlag (for runtime allocations). These flags can
be set to force heap check at each allocation and release to help pinpoint
the source of the problem.
> -----Original Message-----
> From: Carl Lippitt [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 18, 2000 7:29 PM
> To: Palm Developer Forum
> Subject: Hotsyncd.exe debug error DAMGAE
>
>
> What does this mean?
>
> DAMAGE: after Normal block (#133) at 0x01c213e0
>
> ????
>
> Running CDK4, using the hotsyncD.exe (on NT4), and POSE (over
> a network
> WIndows RAS connection on Win 98)
>
> All seems to work if I choose to ignore the pop up dialog,
> but I'd just as
> soon avoid the problem since its a pain having to dismiss
> three of these in
> a row after each apparent DB write to POSE.
>
>
> --
> - - - - - - - - - - - - - - - -
> www.slothware.net
> Carl Lippitt
> DOC/WTG/CTO
>
>
>
> --
> For information on using the Palm Developer Forums, or to
> unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
