1 |
On Tuesday, March 24, 2015 9:32:07 PM Nikos Chantziaras wrote: |
2 |
> On 24/03/15 21:12, Fernando Rodriguez wrote: |
3 |
> > On Tuesday, March 24, 2015 10:07:56 AM Francisco Ares wrote: |
4 |
> >> Hi, |
5 |
> >> |
6 |
> >> Recently - but can't figure out exactly when - Qt Creator has become |
7 |
unable |
8 |
> >> to access Qt containers (where the STL ones work as expected) on the |
9 |
debug |
10 |
> >> panel. It shows <not accessible> in place of the expected item quantity |
11 |
> >> for a QList, for instance, but for a std::vector<std::string>, it works, |
12 |
> >> allowing inspection of all items. |
13 |
> >> |
14 |
> >> Any hints on what I may be doing wrong? The headers are all accessible, |
15 |
for |
16 |
> >> instance. Should I build Qt with debug symbols enabled, as recommended |
17 |
for |
18 |
> >> glibc? |
19 |
> >> |
20 |
> >> Using current Qt 4.8.5, Qt Creator 2.8.1, gdb 7.7.1, gcc 4.8.3 |
21 |
> >> |
22 |
> >> Thanks! |
23 |
> >> Francisco |
24 |
> > |
25 |
> > Try to print it from gdb cli, if it works you'll know the issue QtCreator, |
26 |
> > otherwise you're likely missing some symbols. You should always compile |
27 |
any |
28 |
> > development libraries with debug symbols. |
29 |
> |
30 |
> You don't need debug symbols for inspecting containers. They are not |
31 |
> needed. The only reason for enabling debug symbols in Qt is if you want |
32 |
> to step into Qt's code. |
33 |
|
34 |
Thank you. You do need symbols though, just not Qts for this specific case. |
35 |
There are many reasons why you should compile your development libraries with |
36 |
symbols besides stepping into the code. Such as getting a backtrace. Even |
37 |
proprietary (closed-source) libraries often make the symbols available for |
38 |
this reason. |
39 |
|
40 |
-- |
41 |
Fernando Rodriguez |