Quote Originally Posted by high_flyer View Post
Why??

There is just no reason to do that!
Who knows what you are breaking by doing that.
I repeat all work fine on Windows, and in non-static release on Linux. The error coming with static release on Linux and only when gcc are binding libQtCore.a with my application.

Imagine the new QProcess class like this:

Qt Code:
  1. class Q_CORE_EXPORT QProcess : public QIODevice
  2. {
  3. Q_OBJECT
  4. public:
  5.  
  6. ... all standard methods and variables
  7.  
  8. void setVerifyMutableProcess(bool verify);
  9. bool getVerifyMutableProcess() const;
  10.  
  11. ...
  12. };
To copy to clipboard, switch view to plain text mode 

Quote Originally Posted by high_flyer View Post
Just subclass QProcess, and use your subclass!
I am sure it will eliminate your linking problems as well.
Why?? It's long history.

Well, try to be as brief as possible.

There are some processes in both Windows and Linux, that run they create a new child that is not manipulated from the class QProcess and subsequently the parent is terminated. With this, we lose the links to the application itself because it ended the main thread/process and appeared new children(s) that are kept running. This type of processes/applications I called them "mutable". So, it was necessary to update the "pid" of the class and reconnect QProcess notifiers, pipers and others.

I saw that this was not possible to do from a class inherited from QProcess , or maybe you can tell me more.

Thanks again!