Qt & Memory Leak

[anda_skoa]

If only I could change OS, so easily! My client has already migrated from VxWorks to Cent OS Linux and he has already hundreds of machines installed, yes we could update the OS, this could be done but as you could imagine updating production machines from a tecnological and... well political point of view is not easy

Misunderstanding. I am suggesting to change the OS of the device, I am suggesting to test the application on a different machine, using a different OS and different tools since that is what you seem to have available.

I.e. if your debugger on Windows or OSX can be used to find memory leaks, then run the application on those platforms and use those tools.

To be more clear they are not suprocesses but real processes the master simply forks them

That was my understanding as well. That is what we usually refer to as a subprocess or child process.

We do know thanks to "top" that is the part of "The Application" that is the Qt interface, but we don't know where is the problem...

You could run the Qt interface in valgrind, no?

Here I don't understood well; do you intend to compile only the .so and put in a know application directory and not in a system, one? I've understood correctly?

Yes. You can put the library anywhere you want, you only need to point LD_LIBRARY_PATH to that directory before launching the application.
The runtime linker will look there first before falling back to system locations.

Cheers,
_