Installing extra debugging symbols to use with printers
Da Viper
yerimyah1 at gmail.com
Mon Jul 12 15:50:13 BST 2021
**Using Debugging symbols or not**
**Current Situation**
Some types in QT does not have any information when it is printed out, take
for example `QFile`
we create a QFile like below
```c++
QFile file("/a/path/to/some/place");
```
if try to print this is `GDB` it returns
```gdb
(gdb) p file
$1 = <incomplete type>
```
There are two ways which this problem can be solved i either read the
important variables directly from the memory location or i install
debugging symbols
I am not sure which do, so i ask for some input.
**Why not to use**
- currently i have not seen any pretty printer that requires you to install
debugging symbols in order to use it. (Qt creator or Microsoft visual
studio or existing qt printers do not)
- some distros do not have debugging symbols for qt in its repositories,
e.g arch linux, manjaro but requires you to add another repo
- the debugging process becomes slower than when the symbols are added
(core-dbgsym for console, gui-dbgsym for gui, charts etc this gets slower
the more you add)
**Why to use**
- you can be able to access internal variables with ease
- you can be sure the structure would be the same if there is a new version
(although qt does not change often but some times do if there is a major
version)
- the structure is the same irrespective of the operating system or
architecture
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-finance-apps/attachments/20210712/0a9c0fdc/attachment.htm>
More information about the Kde-finance-apps
mailing list