he rest of the code changes are just that - code
changes, there shouldn't be anything in normal logic to confuse gprof.
Valgrind runs cleanly so it isn't stomping on memory.
Thanks,
David Mathog
[EMAIL PROTECTED]
Manager, Sequence Analysis Facility, Biology Division, Caltech
_
es
(nettee.c:912 @ 804a359)
0.00 0.35 0.0034071 0.00 0.00 readnbytes
(nettee.c:933 @ 804a36a)
What could be the problem in the new version of this program which is so
confusing gprof? I've run nettee in valgrind and it was well behaved
running in there (albeit real
