Qt & Memory Leak

[fanoI]

If you have better tools on other operating systems then I would suggest to use them.
Not sure how a debugger is going to help you there either though.

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

I personally have found valgrind to be a very capable tool for finding all kinds of runtime issues and would wish it would be available for Windows as well (it is available for OSX I think).
Since you have subprocesses you could narrow down the problem considerably by just running one of them at a time and check which one is leaking the memory.
Or maybe you can already see that in top and valgrind only the problematic component

To be more clear they are not suprocesses but real processes the master simply forks them, we call the processes togheter "The Application" but from the OS point of view they are normal applications (they have a main(), I see on ps and top them as all applications, they not share memory and so on), it was no Valgrind the problem it was our IPC that uses the process name to communicate... well it sees Valgrind as all member of "The Application" and all died in atrocious sufference (at least we suffered, "The Application" I don't know... but I hope so ), we tried efence in the past, it find nothing, sadly... we could try again, maybe it help us this time!

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 also just build Qt and deploy it as an application dependency.

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? Well this could help to found a fast solution in this phase of extreme emergency, yes, I could try to propose it...

We could do the RPMs after as we want to use Qt for others "Applications".

The operating system does not see memory leaks, it only sees memory allocations. At some point it can't provide the requested memory anymore.

Yes, I do know it was an overly simplification on my part... the application (the Qt one) leaks memory and so Linux kill it!

Cheers,
[/QUOTE]

Thanks and Good Week End,
fano