From:	James W Sager Iii <sager+@andrew.cmu.edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Has anyone written a debugging tool like this?
Date:	Tue, 20 Mar 2001 19:59:25 -0500
Organization:	Carnegie Mellon, Pittsburgh, PA
Lines:	37
Message-ID:	<YuhznhS00UjC1QnlQ6@andrew.cmu.edu>
NNTP-Posting-Host:	po8.andrew.cmu.edu
X-Trace:	bb3.andrew.cmu.edu 985136557 4136 128.2.10.108 (21 Mar 2001 01:02:37 GMT)
X-Complaints-To:	advisor AT andrew DOT cmu DOT edu
NNTP-Posting-Date:	21 Mar 2001 01:02:37 GMT
X-Added:	With Flames (outnews v2.6)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I'm really bad with keeping up to date with other people's code... So I
was wondering does anyone have a utility for taking the first step of
stripping down a large project?

For example if you had 20.cc files, you'd pass them as arguments.

The ripper utility would add a line of code with an index to every one
of your functions that'd basically do the following when executed:

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.

I was wondering if a program like this already existed, and if not,
would it be worth coding?

- Raw text -