Is your application multithreaded? Thread scheduling under valgrind is very
different from running normally. AFAIK, only one thread runs at a time, which
can both slow down threaded applications substantially and also increase the
chances of hitting a deadlock bug in your code.
-Dave
On Jul 13, 2010, at 2:54 PM CDT, Nicolas Rannou wrote:
Hello,
I'm experimenting some issues using valgrind.
I would like to perform a memory leaks checking in my application.
I do:
_
$ valgrind -v --leak-check=full --track-origins=yes ./bin/gofigure
log.txt
__
where ./bin/gofigure is my application, STATIC-DEBUG build, on ubuntu
10.04 - 64 bits.
If I launch this command, it will just get stuck and I have to exit
valgrind manually (I let it running for one night to make sure that it
is not a time issue).
If I run the program without valgrind it works properly (it opens and
closes automatically).
I'm using valgrind 3.6.0
_
$ valgrind --version
valgrind-3.6.0.SVN
_
It use to work with a previous version of valgrind and a previous
version of ubuntu... (I'm not sure about which ones)
Did somebody already experienced this issue?
Do you have any suggestion about how to solve/track this issue?
Thanks,
Nicolas
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
