https://bugs.kde.org/show_bug.cgi?id=379630
Bug ID: 379630
Summary: false positive std::mutex problems
Product: valgrind
Version: 3.13 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: helgrind
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 105387
--> https://bugs.kde.org/attachment.cgi?id=105387&action=edit
test code
If an std::mutex goes out of scope and a new mutex happens to be allocated at
the same address helgrind still remembers the old mutex, leading to strange
behavior.
In the test case attached a lock order violation is reported.
In my actual application the second mutex is a pthread rw mutex and when
locking it I get:
Helgrind: ../../helgrind/hg_main.c:307 (lockN_acquire_reader): Assertion
'lk->kind == LK_rdwr' failed.
It seems Helgrind does not detect when a std::mutex is deallocated.
Linux eselivm2v1074l 2.6.32-504.3.3.el6.x86_64 #1 SMP Fri Dec 12 16:05:43 EST
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are watching all bug changes.
