|
From: Benjamin M. <be...@me...> - 2007-08-28 22:45:25
Attachments:
callgrind_decompress.tar.bz2
|
Sat down this evening and wrote a tiny tool to decompress a callgrind file. In the event you forget to use "--compress-strings=no -- compress-pos=no" You can just pass the callgrind file to this tool and it will spit out a uncompressed version of it (that is easier to manually read). It is fast and takes just a few seconds to expand an average callgrind file. It is hardcoded to support "positions: line", but it wouldn't take much work to expand that. It uses Qt for the convenience of its file/string/tools, but you could convert it to stl if you want. To build it run qmake (qmake- qt4 on debian) and then make. BSD licensed -Benjamin Meyer |
|
From: Josef W. <Jos...@gm...> - 2007-08-28 23:26:22
|
On Wednesday 29 August 2007, Benjamin Meyer wrote: > Sat down this evening and wrote a tiny tool to decompress a callgrind =20 > file. In the event you forget to use "--compress-strings=3Dno --=20 > compress-pos=3Dno" You can just pass the callgrind file to this tool =20 > and it will spit out a uncompressed version of it (that is easier to =20 > manually read). It is fast and takes just a few seconds to expand an =20 > average callgrind file. It is hardcoded to support "positions: =20 > line", but it wouldn't take much work to expand that. =46rom a brief look, you seem to leave the IDs used for string compression in. It is better to get rid of them in the uncompressed version. Otherwise, it looks fine. Josef > It uses Qt for the convenience of its file/string/tools, but you =20 > could convert it to stl if you want. To build it run qmake (qmake-=20 > qt4 on debian) and then make. BSD licensed >=20 > -Benjamin Meyer >=20 >=20 |