Author: njn Date: 2007-09-21 06:51:26 +0100 (Fri, 21 Sep 2007) New Revision: 6889
Log: update Modified: branches/MASSIF2/massif/ms_main.c Modified: branches/MASSIF2/massif/ms_main.c =================================================================== --- branches/MASSIF2/massif/ms_main.c 2007-09-21 05:50:30 UTC (rev 6888) +++ branches/MASSIF2/massif/ms_main.c 2007-09-21 05:51:26 UTC (rev 6889) @@ -32,25 +32,17 @@ //--------------------------------------------------------------------------- // Todo: // - do a test for realloc -- I think no snapshots are being taken for it. -// - do a test where the time exceeds 32-bits -// - do a test with no allocations -- bar should be zero sized in graph? // - do tests with complicated stack traces -- big ones, ones that require // XCon_redo, etc. // - test what happens when alloc-fns cover an entire trace // - write a good basic test that shows how the tool works, suitable for // documentation -// - try to write a -v test. how to filter the Valgrind -v stuff out? Have -// --ms-verbose, which is implied by -v but also able to be turned on -// separately? -// - get snapshot frequency right after some have been discarded // - Check MALLOCLIKE_BLOCK works, write regtest // - clean up structure of ms_print // - work out peak-taking // - make everything configurable, eg. min/max number of snapshots (which // also determine culling proportion), frequency of detailed snapshots, // etc. -// - have a test with lots of zero-sized allocations -- makes sure that -// timespans of 0 between snapshots is ok... // // Misc: // - with --heap=no, --heap-admin still counts. should it? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
