Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Call for Presentations - Qt World Summit

    Solved What are the causes of abrupt termination of a program with Qt6?

    Qt 6
    qtcreator c++ qt
    2
    2
    250
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gouneken last edited by

      Hello, I have been working on a two window project for some time and just finished editing the code for the first window. But, when I compile, the IDE writes an error message saying "Gross program shutdown at 19:36:39", I don't know why my program abruptly terminated, this is the first time that This happens to me, however, no coding error was generated, not even warnings. I am writing this post because I would like to know (if any) the most common causes of a program crashing with Qt6 (I use the QtCreator IDE), not for my project, but in the general case of Qt projects and how to solve these problems.

      Thank you for your attention!

      1 Reply Last reply Reply Quote 0
      • mrjj
        mrjj Lifetime Qt Champion last edited by

        Hi
        The normal way to find out what is going on is using the debugger.
        So compile the app In debug mode and start it.

        When it crashes you should be able to see what it was doing in the call stack.
        The call stack is the area under the editor window when starting in debug mode

        alt text

        As you can see it shows where the program was running.
        The function list.

        This should give a hint as to why it does crash.

        1 Reply Last reply Reply Quote 2
        • mrjj
          mrjj Lifetime Qt Champion last edited by

          Hi
          The normal way to find out what is going on is using the debugger.
          So compile the app In debug mode and start it.

          When it crashes you should be able to see what it was doing in the call stack.
          The call stack is the area under the editor window when starting in debug mode

          alt text

          As you can see it shows where the program was running.
          The function list.

          This should give a hint as to why it does crash.

          1 Reply Last reply Reply Quote 2
          • First post
            Last post