Date: Wed, 21 Mar 2001 12:18:19 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: James W Sager Iii cc: djgpp AT delorie DOT com Subject: Re: Has anyone written a debugging tool like this? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 20 Mar 2001, James W Sager Iii wrote: > When your program starts up, a global binary output file would open. > It would initialize to 0's from 0 to the number of functions you have in > your program. > > Then each time a function is called, it'd update the index in the output > binary file to 1. > > How it'd work: > > You just run your code as normal. > > But if you get a tricky memory leak bug, and your project is huge, > you'll want to start cutting your project down into little pieces to > isolate it. This ripper utility would take the first step for you. > > You run ripper part 1, and it spawns the functions and indicies into your code. > > You compile and run until you hit the bug in the code. > > You then run ripper part 2, and it removes every function that wasn't > used, and outputs new files for you to make debugging easier. There's `gcov', a coverage analysis tool that is part of GCC. Current GCC ports don't include gcov.exe, but I'm told that the next one will.