Public bug reported:
Binary package hint: g++
A fairly complex application using boost threads on amd64 suffers from
memory corruption bugs when compiled with g++ 4.3. When using g++ 4.2
the problem goes away. The corruption always occurs shortly after
creating a new thread. I've tried several versions of boost (34, 35, 36
and 37) and I believe it is not boost related.
To speed up locating this problem I used DUMA, a derivative of electric
fence. Electric Fence btw does not work properly on 8.10/gcc-4.3. The
problem is that pthread mutexes are not enough to protect the library
from re-entrance, in DUMA this problem is solved using semaphores. And
the symptoms when using Electric Fence along with the g++-4.2 compiler
are very similar to the problems I had with code created with g++-4.3.
Is there any 'operator new' code using pthread mutexes that can be
called from thread initialization code?
If I need to do more to investigate this problem, please contact me.
** Affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
--
code generation bug in gcc 4.3.2 / amd64 / 8.10
https://bugs.launchpad.net/bugs/305056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
