On Sunday 08 June 2003 02:57 am, Guillaume Laurent wrote: > If I understood you correctly you want to use (cache|val)grind on RG ? Then > I don't see why you need to recompile the whole of Qt/KDE. Only RG needs to > have debug info in (unless you're tracking a bug which ends up being a KDE > bug and thus really need stacktraces going that deep).
Here are some snippets from the README_KDE3_FOLKS file in the valgrind distribution: ``* You need to compile the KDE to be debugged, using a decent gcc/g++:" ``* Build as much of KDE+Qt as you can with -g and without -O, for the usual reasons." So, this is what I went ahead and did. It made the compiled code EXTREMELY huge (well, I went haywire with Qt and added -g3 and -ggdb to the spec file). For example, check out this monstrosity: non-debug: 6.5M /usr/local/qt/3.1/lib/libqt-mt.so.3.1.2 debug (-g3): 85M /usr/local/qt/3.1-debug/lib/libqt-mt.so.3.1.2 So yes, my goal is to start using valgrind (and gdb). -- Levi Burton http://www.puresimplicity.net/~ldb/ ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
