From: adu <ad...@na...> - 2009-09-22 14:21:37
|
Hi! First of all I want to thanks for such amazing program)) But there are still some problem/misunderstandings and etc )) First of all we have 3 links http://valgrind.org/downloads/guis.html http://www.open-works.net/projects/valkyrie.html http://valgrind.org/downloads/current.html The first 2 of 'em - are talking about 1.3.0 version even there is already 1.4.0! And (I hope very) soon there will be 1.5.0 version))) Maybe someone has to change all those places in one manner? Whereupon - here it is very difficult question - well, how much time (approximately of course) it is necessary to wait till the moment of release of the new version? I understand what all is relative - but nevertheless is here quite certain milestone? In the second: I suggest adding not only support for 3.5 version of valgrind but also introduce new feature in valkyrie itself: 1. Selecting of node of errors tree and to call context-menu. Which will contain (for now) only 1 item - <Copy error in clipboard>? And hereby we will have error as a 'plain formatted text' - we will have representation of current selected error from the global errors tree for a future using. For ex. I (as a Tester) can send to developers only small (but useful) piece of valgrind log. Because right now I HAVE TO create and to send ALL log. Of course such trick should work only with first-level nodes. 2. Filters for valgrind output in main window. Right now we can see (in situation with a real huge amount of errors) very loooooong error's listing in main window - and sometimes to open each kind of found error from this list and make something useful in source code for removing this error - is quit difficult because this list is very looong. BUT - If we had an opportunity to use Filter-system then we would reduce quantity of errors on the screen and the correction of mistakes would be more comfortable. I suggest making filters based on the basic fields of the xml structures describing one error: TAG <obj> - filters:["equal","contains", "starts with", "ends with"] TAG <fn> - filters:["equal","contains", "starts with", "ends with"] TAG <dir> - filters:["equal","contains", "starts with", "ends with"] TAG <file> - filters:["equal","contains", "starts with", "ends with"] And also - for more gobal tags like: TAG <kind> - filters:["equal"] {here should be only predefined list of error types} TAG <leakedbytes> - filters:["equal","more that", "less than", "from .. till .."] And final question: How I can suppress annoying STL errors?problems? Ex.: <frame> <ip>0x5AF17F4</ip> <obj>/usr/local/tools/gcc/gcc-3.2.3/lib/libstdc++.so.5.0.3</obj> <fn>std::string::append(char const*)</fn> <dir>/usr/local/samba/download/Redhat9/addons/gcc/gcc-3.2.3/gcc-build2/i686- pc-linux-gnu/libstdc++-v3/src</dir> <file>/usr/local/samba/download/Redhat9/addons/gcc/gcc-3.2.3/gcc-build2/i686 -pc-linux-gnu/libstdc++-v3/include/bits/char_traits.h</file> <line>135</line> </frame> Yes, I've read about .supp files but I don't have it on my comp. Only in valgrind dir I have few of 'em - but they not covering gcc and STL functions... Where I can find rather big && useful .supp files?? Regards, Anton |