Replies: 6 comments 1 reply
-
Sorry, I've no idea what "python from qtcreator" is... Are those LLDB data formatters? That should have worked. CodeLLDB uses a fairly normal LLDB underneath. |
Beta Was this translation helpful? Give feedback.
-
Yes, lldb data formatters. |
Beta Was this translation helpful? Give feedback.
-
Mostly things for better Rust support, otherwise it's pretty stock.
Could you please be more specific? |
Beta Was this translation helpful? Give feedback.
-
The crash was similar to this one here #514 But that it is not what I'm after. My problem is the data formatting. |
Beta Was this translation helpful? Give feedback.
-
I was able to solve the problem. For anyone who might run into something similar: Then with Qt's lldbbridge.py it is possible to look at least into the QString and get a little information (e.g. size of QVector) for other structures. Then I tried the qt.py (need to be updated to python3) from KDevelop with a little more luck: I can view QMap/QVector internals now, but for some reason QString is not working for me. Anyhow, all of this is not CodeLLDB related. |
Beta Was this translation helpful? Give feedback.
-
Yes, it helps. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have taken CodeLLDB into use and it's working pretty good (and compared to gdb really fast).
I can also inspect data. There is only one problem:
The application I am debugging is a Qt application and I am not able to look into the Qt data structures.
One thing I tried was to take the python from qtcreator and made lldb load it in "initCommands".
But still I can't look into the data structures.
Any advise how this can be achieved.
Beta Was this translation helpful? Give feedback.
All reactions