X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Mon, 19 Apr 1999 16:52:22 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp workers list <djgpp-workers AT delorie DOT com>
Subject:	Re: Probblem: Debug info COFF vs. stabs
In-Reply-To:	<Pine.SUN.3.91.990419174057.14514E-100000@is>
Message-ID:	<Pine.LNX.3.93.990419164852.6515V-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 19 Apr 1999, Eli Zaretskii wrote:

> 
> On Mon, 19 Apr 1999, Hans-Bernhard Broeker wrote:
> 
> > During my work on making as much of the functionality of recent 'gprof'
> > work on DJGPP (line-by-line profiling, static call graph by code
> > inspection, basic block counts from 'gcc -a'),
> 
> Is anything of these niceties available for use?  Line-by-line profiling 
> was long on my todo list, and would be really nice to have.

I would have made them available if not for those problem with the two
styles of debug infos. I have some patches at home, some for gcc (the '-a'
profiling is broken since the '-ax' one was introduced, in the original
FSF sources, and '-a' output is not written to a gprof-style file), others
for BFD (fix and speed up the 'find_nearest_line' function for COFF and
stabs, partly off the net)  and gprof itself. 

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -