Hi Philippe,

The executable not recognised thing is a red-herring I'm sure.

The problem seems to be some kind of process-level lock on locale resources. 

A single instance of valgrind over all our processes runs fine.  The issue is not the application, it is the parallelisation that I have introduced by using Python's multiprocess module in order to run batches of valgrind together.  One valgrind instance takes about a week to run over all our processes which is why I started to explore the multiprocess route.  For the moment, I'll scale back and be patient until I understand the locale issue.

Thank for your help.


On Tue, Feb 11, 2014 at 8:32 PM, Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:
On Tue, 2014-02-11 at 07:22 +0000, David Carter wrote:
> Hi Philippe,
> Thanks for your suggestions, I have got the first part of the
> information.  It seems there is some contention over locale
> resources.  Do you agree?
Well, difficult to say without looking more in depth at the code.
Taking into account that there are threads still running,
that the valgrind trace shows that threads are being scheduled,
I guess the problem is linked to the application, not to valgrind.

It looks to me that the easiest would be to have a way to
debug the application, trying e.g. a newer gdb and vgdb
(if the newer gdb supports the strange executable format).

Alternatively, just make a normal executable :).

At this stage, not much can be done from Valgrind side I am afraid.