how about profile ?

how about profile ?

Posted Oct 18, 2003 21:55 UTC (Sat) by johnjones (subscriber, #5462)
Parent article: Researchers take debugging to the masses (News.com)

it does not do much what would be nice would be to profile the programs as well to find
hotspots....

HOTSPOTS (maybe cachegrind) and things like valgrind to find memory leaks would be
nice....

they say -
<i>"
Just before each instrumented application exits, it sends a feedback report up to our
collection server here at Bug Isolation Headquarters. That report includes:

application report:

name, version, and release of the application
type, version, and density of instrumentation used
outcome: exit status returned or fatal signal received

samples report:

list of loaded, instrumented code modules (main application, plugins, etc.)
observed predicate counters for each module

If the program received a fatal signal, then the feedback report also includes crash details:

list of loaded shared libraries at the time of failure
stack trace for each thread at the time of failure
</i>

---

(Log in to post comments)