On Tuesday 06 November 2012 22:56:32 Philippe Waroquiers wrote:
On Tue, 2012-11-06 at 13:43 +0100, David Faure wrote:
On Monday 05 November 2012 23:19:42 Philippe Waroquiers wrote:
On Mon, 2012-11-05 at 18:59 +0100, David Faure wrote:
The testcase
Hi,
Valgrind is great, and I've no problems using it under Linux.
However, I also must work on a Mac (running Mac OS Lion), and there I do
have couple of problems:
#
1) Native gcc compiler on Mac OS is very
On Wed, 7 Nov 2012 15:51:10 +0100, Anton Popov said:
1) Native gcc compiler on Mac OS is very old (version 4.2).
That's because Apple has switched from gcc to clang.
Have you tried just building with the default 'cc' compiler provide by Xcode?
Cheers,
--
On Wed, 2012-11-07 at 16:54 +0100, Matthias Schwarzott wrote:
Printing thread names is not a bad idea (not too sure that a lot
of applications are using pthread_setname or prctl but never mind).
In any case, I see several subtilities to look at.
Using plain gdb, info threads also lists these
On 11/7/12 5:30 PM, Sean McBride wrote:
On Wed, 7 Nov 2012 15:51:10 +0100, Anton Popov said:
1) Native gcc compiler on Mac OS is very old (version 4.2).
That's because Apple has switched from gcc to clang.
Have you tried just building with the default 'cc' compiler provide by Xcode?
On Wed, 2012-11-07 at 10:51 +0100, David Faure wrote:
The idea of helgrind is that it detects lock order problems and/or
race condition problems *even* if no deadlock happens and/or if no
race condition really happened.
Maybe it is very unlikely that the trylock fails. Still would be nice
On Wednesday 07 November 2012 23:00:51 Philippe Waroquiers wrote:
On Wed, 2012-11-07 at 10:51 +0100, David Faure wrote:
The idea of helgrind is that it detects lock order problems and/or
race condition problems *even* if no deadlock happens and/or if no
race condition really happened.
