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

16:24:37: The program has unexpectedly finished.



  • This post is deleted!


  • Using the debugger - with thoughtfully set breakpoints - is usually the best bet to quickly find and eliminate a problem. However, I often make extensive use of debugging output, especially if the problem is hard to reproduce. That way I can narrow down the whereabouts of the origin.



  • @AnneRanch
    If you are lucky you will not have to "step thru". Simply run the program from the debugger. Hopefully when the "crash" happens it will stop and the debugger will will kick in. Then all you have to do is examine the stack trace window and trace back to a line in your code which caused the problem. Without needing to place breakpoints or do any stepping.



  • Well - after enabling "stop when abort..."

    e5f1c373-9b48-4034-b7b2-584c5af67ab7-image.png

    and removing all breakpoints up to suspected problem and running "debug" I am getting this

    4dd1697e-a667-418e-a7d3-9130994e091c-image.png

    which really does not help much to identify the problem area.
    I guess I will experiment more with the "GDB extended" options.

    Actually wonder what "reverse debugging" does.



  • @AnneRanch said in 16:24:37: The program has unexpectedly finished.:

    which really does not help much to identify the problem area.

    Yes, it does. I you read my answer and act on it

    Then all you have to do is examine the stack trace window and trace back to a line in your code which caused the problem.



  • @AnneRanch

    "Segfault" indicates what kind of issue you are facing (probably some bad/unallowed memory access).
    Debug and check for example if you manually delete something before the crash.


Log in to reply