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

QtCreator crash & no debug info



  • Hey

    I'm a bit lost. I have a QGraphicsView / scene with some items in it. When I try to do an operation on it I get a crash, but the debug looks like this :

    c95c1d67-9c12-42a2-a663-25cc5030715c-image.png

    I tried stepping line by line, but as far as I can tell, once I release mouse everything runs as it should in my code, then it goes into Qt internal code and crashes there...

    How can I debug it?


    Edit VS provide this ertror :

    3b471bd9-9f3a-41b3-aa71-41ef74c1e0f8-image.png


  • Lifetime Qt Champion

    Hi @Dariusz,

    looks like some recursion here...

    Is there anything meaningful when you click More on the stack view?

    Otherwise you'll need to show some code.

    Regards



  • @aha_1980 said in QtCreator crash & no debug info:

    Hi @Dariusz,

    looks like some recursion here...

    Is there anything meaningful when you click More on the stack view?

    Otherwise you'll need to show some code.

    Regards

    Sadly nothing I could use... mostly what you can see above.

    I will try looking for recussion, I know I fire lots of "update()" calls during the action but not sure.

    Essentially I do a connector drag - mousemove/release calls to simulate node editor connection move.

    Will try to narrow it down somehow.

    TIA



  • Still getting dem crashes...

    I think the issues is that I call update() from graphicsItem, and then I do delete item. So perhaps I have racing condition when the QT try to update the viewport but fails because I called delete on the item?

    I don't see any deleteLater() on graphics items so how should I remove them from the viewport?

    TIA


  • Lifetime Qt Champion

    @Dariusz

    As said above, without showing you code it's just guessing.

    If you cannot show the whole code, try to create a minimal reproducing example. Often you find the solution while doing so.

    Regards


Log in to reply