Debugging a Qt-library
-
Then I am a bit lost with your question.
So you successfully built and used the custom version of the module yet it seems that your modifications are not taken into account ?
-
Then I am a bit lost with your question.
So you successfully built and used the custom version of the module yet it seems that your modifications are not taken into account ?
-
Hence my question: did you install your custom built module ? Just building it is not enough.
-
Hence my question: did you install your custom built module ? Just building it is not enough.
-
Hence my question: did you install your custom built module ? Just building it is not enough.
-
@SGaist So how do I install it? I have only changed a single line of code, so I just want to sort of "update" the standard module.
@Rasmunis
So you have built it but not installed it anywhere that your application will pick up from. You either need to do a full build and go through the installation process for Qt for building from source, or if you are sure you have built exactly the same version of Qt as you presently have in all its shared libraries you could identify the single shared library (.soor.dll) this source file contributes to and just (temporarily) replace that with your newly compiled version. If you intend to debug-step into your new code, you will also have to ensure that your source file is found by the debugger. -
@SGaist So how do I install it? I have only changed a single line of code, so I just want to sort of "update" the standard module.
-
@JonB you don't need a full Qt build to build one module for the Qt version you are currently using however you are right about making a backup of the files related to the module you are going to hack on if you don't have your own build.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
@JonB you don't need a full Qt build to build one module for the Qt version you are currently using however you are right about making a backup of the files related to the module you are going to hack on if you don't have your own build.
@SGaist said in Debugging a Qt-library:
@JonB you don't need a full Qt build to build one module for the Qt version you are currently using
Indeed not, but do you wish to guarantee that the user is rebuilding one library against an existing build/system-supplied which is deffo, deffo the same version, compiled in the same way etc.? :) Because I can hear "version mis-match" in the distance... ;)
-
I tried @JonB 's approach and it worked for me. And I did manage to remove the memory-leak, which makes me think that this is a bug in the library. How do you suggest to move forward with this?
@jsulm Where do you execute the make-commands? I have yet to find any makefiles.
Edit: I found the makefile in the build-folder.
-
I tried @JonB 's approach and it worked for me. And I did manage to remove the memory-leak, which makes me think that this is a bug in the library. How do you suggest to move forward with this?
@jsulm Where do you execute the make-commands? I have yet to find any makefiles.
Edit: I found the makefile in the build-folder.
@Rasmunis said in Debugging a Qt-library:
How do you suggest to move forward with this?
File a bug in Qt bug tracker: https://bugreports.qt.io/projects/QTBUG/issues
"Where do you execute the make-commands?" - where you build Qt.
configure ... make make install -
After the bug report, since you have a fix, you can submit a patch for inclusion :-)
