RE: debuging memory leak

From: Plus/4 <Plus/4@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Apr 2005 01:22:02 -0700

Hi Andrew!

The problem is localised by the debugger itself, you see:
> {86} normal block at 0x00DF2D90, 24 bytes long.

means 86th line...Maybe it's in your own code, check it out...
.

Follow-Ups:
- Re: debuging memory leak
  - From: andrew

References:
- debuging memory leak
  - From: andrew

Prev by Date: Displaying Frame While Moving
Next by Date: Re: Difference between CRegKey::QueryStringValue and RegQueryValueEx
Previous by thread: debuging memory leak
Next by thread: Re: debuging memory leak
Index(es):
- Date
- Thread