From: Philippe E. <ph...@us...> - 2004-02-17 05:16:20
|
Update of /cvsroot/oprofile/oprofile In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30428 Modified Files: ChangeLog TODO Log Message: clarify opstack header; use 0 istnead of 0.0e+00 Index: ChangeLog =================================================================== RCS file: /cvsroot/oprofile/oprofile/ChangeLog,v retrieving revision 1.1468 retrieving revision 1.1469 diff -u -p -d -r1.1468 -r1.1469 --- ChangeLog 16 Feb 2004 17:36:48 -0000 1.1468 +++ ChangeLog 17 Feb 2004 05:07:42 -0000 1.1469 @@ -1,3 +1,10 @@ +2004-02-17 Philippe Elie <ph...@wa...> + + * libpp/format_output.cpp: use "self/child" for header + * libutil++/string_manip.cpp: format_percent() return "0" if + value == 0.0 + * libpp/callgraph_container.cpp: remove some dead code. + 2004-02-16 Philippe Elie <ph...@wa...> * module/compat24.h: Index: TODO =================================================================== RCS file: /cvsroot/oprofile/oprofile/TODO,v retrieving revision 1.375 retrieving revision 1.376 diff -u -p -d -r1.375 -r1.376 --- TODO 16 Feb 2004 20:08:34 -0000 1.375 +++ TODO 17 Feb 2004 05:07:42 -0000 1.376 @@ -6,13 +6,11 @@ for some pointers and/or read HACKING an 0.8 release ----------- - o print "0" not "0.0e+00". should we consider reworking opstack output -format? make the headers more explanative + o should we consider reworking opstack output format? o TRACE_END is no longer sent by the driver, keep it a bit for compatibility o callgraph_container.cpp: the inner loop in add() is very fragile! o We must define and choose the meaning of output - o recursive call count are wrong. FIXME: unsure but now I think it comes from - the way we show results, ours results are ok. + o self sample for recursion are wrong o Test all other opstack options. o review opstack documentation, improve it by giving examples of output and how to interpret it. @@ -20,7 +18,8 @@ format? make the headers more explanativ o opstack --acumulate (fix it or inhibit) ? o callgraph patch: better way to skip ignored backtrace ? - o can daemon avoid to hack about last_is_kernel ? + o can daemon avoid to hack about last_is_kernel ? No, non callgraph driver + in 2.6 get the same problem and we must be compatible. 0.9 release ----------- |