Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

General Issues in using QT creator:



  • Hello everyone,
    Recently while using QT creator came across certain issue would like to know your opinion on the same:
    The issue are mainly based on the thread below which have been solved:
    https://forum.qt.io/topic/103330/issue-with-the-thread

    Issues:

    1. Unable to use the debug mode when included a library built in release mode.
      -> I am working on windows 10 platform recently i had to use tensorflow for which only release mode library was available.
      So when i included the library and run my program it debug mode it would give me an error: failed to initialized the gdb.
      Can anybody provide explanation for the issue ?

    2. When i used cout and qDebug() together. The cout element used to get printed first than randomly at any instant of time qDebug used to print its log.
      -> I have observed that cout endling with endl gets printed first than the qDebug.
      -> There are certain times for example when i use opencv along with qt to print some logs i needed cout for ex: size of an image.
      -> To print the qt logs for example if i need to get the QList element i used to qDebug(). At that time unordered logs created a lot of confusion.
      Is there any solution for the same ?

    3.Some time when i add a file to pro file the and build the program it doesn't gets included
    ->It often occur so i have to delete build folder and rebuild it for the files to get included.
    -> I came across certain forums which said that this was not required but the solution and explanation was not clear.



  • @Kira said in General Issues in using QT creator::

    Some time when i add a file to pro file the and build the program it doesn't gets included

    Which kind of file did you add c++/h file with SOURCES += or HEADERS += ?
    In this case, saving the project file should rerun qmake and so create a new Makefile.
    if not, simply right click on project and select Run qmake (or with Build/Run qmake)



  • @KroMignon : Ohhk sure. Will try :)


  • Lifetime Qt Champion

    @Kira said in General Issues in using QT creator::

    Unable to use the debug mode when included a library built in release mode.

    Under Windows, this is not supported. Debug and release libraries might use different (incompatible) versions of the C runtime which can lead to undefined behavior including crashes. That is the reason why Qt libraries exists as (large) Debug and (small) Release libs on Windows.

    Note that this is a general problem, not a Qt or Creator problem.

    Regards



  • @aha_1980 said in General Issues in using QT creator::

    @Kira said in General Issues in using QT creator::

    Unable to use the debug mode when included a library built in release mode.

    Under Windows, this is not supported. Debug and release libraries might use different (incompatible) versions of the C runtime which can lead to undefined behavior including crashes. That is the reason why Qt libraries exists as (large) Debug and (small) Release libs on Windows.
    Note that this is a general problem, not a Qt or Creator problem.

    I assume this means statically linked libraries? Or does this apply to dlls as well? At some point a debug program has to access system dlls to run at all.


  • Lifetime Qt Champion

    @fcarney said in General Issues in using QT creator::

    Or does this apply to dlls as well? At some point a debug program has to access system dlls to run at all.

    It does apply to DLLs. I cannot tell you more about this, you can google a bit around or see for example https://bugreports.qt.io/browse/QTCREATORBUG-21821

    And as said, it might work, it's just not guaranteed.

    System DLLs seems not to apply to this. Maybe system they are not affected because they are not using C++ ? I really cannot tell.

    Regards



  • @aha_1980 said in General Issues in using QT creator::

    It does apply to DLLs.

    Dang it. I searched a bit and it comes down to runtime libraries using different representations for objects. I also found this. Thanks for setting us straight.



  • Thanks everyone for your replies


Log in to reply