On Mon, 03 Dec 2012 12:49:04 +0100 Massimo Maiurana <maiur...@gmail.com> said:
> Carsten Haitzler (The Rasterman), il 03/12/2012 01:50, ha scritto: > > > did you run valgrind by hand on enlightenment_start itself? or did u use the > > -valgrind option for enlightenment_start ? > > I used the xnitrc-debug in the wiki, and it runs valgrind which in turn runs > enlightenment start. > the complete command is the following: > > exec valgrind --tool=memcheck --db-attach=yes --num-callers=32 \ > --show-reachable=no --read-var-info=yes --leak-check=full \ > --leak-resolution=high --undef-value-errors=yes \ > --track-origins=yes --trace-children=yes \ > $e17_install_path/bin/enlightenment_start 2>&1 | tee -a "$log_file" it's not tracing e itself... :( enlightenment_start -valgrind=1 :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
