You can refer http://www.linuxjournal.com/article/6556
and

http://msdn.microsoft.com/en-us/library/ms859415.aspx

Quote from MSDN :
*"**Basically, you can spot a memory leak when you detect an unexplained
increase in either committed system memory—memory used by various
applications—or in memory owned by a specific application. There are several
approaches to take for checking the current memory situation, as follows:
..... "*

   - *Run the mi command. At the cesh prompt, type mi. This command
   generates a list of memory usages for each running application. In the Page
   Summary line specified for each application, you will see “r/w=” followed
   immediately by a number. This number indicates the number of allocated pages
   of memory for the indicated application. If this number is unexpected or has
   grown unexpectedly, you may have detected a memory leak in the indicated
   application.*


On Tue, Aug 16, 2011 at 10:56 PM, Jacob Ridley <[email protected]>wrote:

> Use WinDbg->UMDH to find which stack is making more allocations.
>
> On Aug 15, 3:03 am, SAMMM <[email protected]> wrote:
> > How to detect in which line the Memory Leak has occured ?? I want the
> > line number where the Memory leak occurs ??? Give every wild answer u
> > can think off ............
>
> --
> You received this message because you are subscribed to the Google Groups
> "Algorithm Geeks" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/algogeeks?hl=en.
>
>


-- 
Regards
Rajeev N B <http://www.opensourcemania.co.cc>

"*Winners Don't do Different things , they do things Differently"*

-- 
You received this message because you are subscribed to the Google Groups 
"Algorithm Geeks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/algogeeks?hl=en.

Reply via email to