On 25/02/15 06:05, SHEHAB ZAINELDINE wrote:

> That would mean, that locking the same lock twice in a row should
> trigger helgrind to stop the program and give me the error, but what
> happens is that the deadlock is allowed to happen. I there something
> that I am missing, or is that a bug?

Why do you think that is what "should" happen?

That is not how valgrind handles errors - it reports problems and then 
allows execution to continue.

Tom

-- 
Tom Hughes (t...@compton.nu)
http://compton.nu/

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to