-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request, better debugger intergration with QT #1721
Comments
Thank you for the feature idea. We will analyze and triage it. In the mean time, since I am not very familiar with this, just give a few more details about this visualizerFile, what should the extension do exactly. |
when launch the debugger, specify the visualizerFile properly |
@lygstate Please let me know if I can provide further information. |
I think this feature could be done as a part of #1394 |
@CComparon "cmake.debugConfig": {
"visualizerFile": "${workspaceFolder}/.vscode/qt5.natvis.xml",
"showDisplayString": true,
}, in my case this snippet in |
This approach will lead to serious performance losses. I have found a better solution. {
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${command:cmake.launchTargetPath}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [
{
"name": "PATH",
"value": "$PATH:${command:cmake.launchTargetDirectory}"
}
],
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": false
}
],
}
]
} setup the command enable pretty-printing for gdb, and set qt5printing, You can get the same result, and there is no longer a lag in the debug process. |
Qt 6.0 are using cmake by default, and cmake have better support for qt now.
For debugging with QString and other Qt object, we need visualizerFile for debugger,
so we need automatically specify the visualizerFile automatically when the project are depends on Qt
The text was updated successfully, but these errors were encountered: