Conditional breakpoint?

[SPlatten]

@JoeCFD , thank you, so I did this right clicking the member variable with a breakpoint set on a line, however I'm not sure this is what I want as the breakpoint will stop on the line where the breakpoint was created. I want a breakpoint that will halt at the location where the condition is true.

[JoeCFD]

@SPlatten add as many as you want with the same condition and you will catch it somewhere. As soon as you reach the breakpoint which meets the condition, you can trace back.

[SPlatten]

@JoeCFD , the problem is I don't know what is making the change or where, all I can say is I have one instance of an object which has a QFormLayout when I add a widget to it, its there and at some point between the next call to add the next widget, the previous widget is no longer there. I really don't know why.

[JonB]

@SPlatten
You cannot set a breakpoint in the way you would like. That would require the list to be monitored as every instruction is executed. I don't think gdb or even MSVC offers this.

[SPlatten]

@JonB , thank you, ok, I'm open to suggestions on how I might track down why the behaviour I'm seeing is occurring.

[JonB]

@SPlatten
I know, I'm thinking about it. But doesn't mean I'll come up with anything... :)

[JoeCFD]

@SPlatten if you know which widget disappears(you should know by setting object name or id), create a shared point of it. Check if the shared pointer becomes nullptr at the steps where it may disapppear.

[JonB]

@JoeCFD said in Conditional breakpoint?:

at the steps where it may disapppear.

The point is @SPlatten does not know where it may disappear.....

[SPlatten]

@JoeCFD , I've called setObjectName on all the widgets I'm using, not sure how this helps tho.

[JoeCFD]

@SPlatten when the widget is created with that object name, you assign it to the shared pointer. You use break points to go down step by step to check if the shared pointer is null or not. Then you will know exactly where it disappears.

[JonB]

@SPlatten
Very first thought: can you at least put a debug on the QObject::destroyed() for the object that goes missing? Find out whether that is happening.

And/or listen to what @JoeCFD is saying, I've never used a shared pointer but he obviously has!

[SPlatten]

@JonB , I'm not sure that the widget itself is being destroyed at all, only that it isn't in the list I appended it to when I go to add the next widget.