public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [OFF TOPIC] Qt Creator unable to access containers in debug mode
Date: Wed, 25 Mar 2015 00:32:30 +0200	[thread overview]
Message-ID: <mesolu$oob$1@ger.gmane.org> (raw)
In-Reply-To: <CAHH9eM6KivAzw2VPt4fhycY9tQDWPCXSpMiaH+CU8m5tAmBepg@mail.gmail.com>

Note that gdb cannot inspect containers. It doesn't know anything about 
them.

Qt Creator uses "debugging helpers" for that. See:

   https://qt-project.org/doc/qtcreator-2.8/creator-debugging-helpers.html

Since you're using a deprecated version of Creator (2.8 is from 2013 and 
not maintained anymore), those helpers are probably not updated for new 
gdb versions.

If you don't want to upgrade Creator through portage, you could instead 
use the binary Qt Creator installer, and simply install it in your home 
directory (I did that in the past, before Qt5 was put in ~arch.)


On 24/03/15 22:43, Francisco Ares wrote:
> Thank you all for those clues, pretty interesting.
>
> For now I suppose it is a gdb thing, as QtCreator is able to show
> details about STL containers as expected.
>
> Going to fiddle in gdb a bit more...
>
>
> 2015-03-24 17:07 GMT-03:00 Fernando Rodriguez
> <frodriguez.developer@outlook.com
> <mailto:frodriguez.developer@outlook.com>>:
>
>     On Tuesday, March 24, 2015 9:32:07 PM Nikos Chantziaras wrote:
>      > On 24/03/15 21:12, Fernando Rodriguez wrote:
>      > > On Tuesday, March 24, 2015 10:07:56 AM Francisco Ares wrote:
>      > >> Hi,
>      > >>
>      > >> Recently - but can't figure out exactly when - Qt Creator has
>     become
>     unable
>      > >> to access Qt containers (where the STL ones work as expected)
>     on the
>     debug
>      > >> panel.  It shows <not accessible> in place of the expected
>     item quantity
>      > >> for a QList, for instance, but for a std::vector<std::string>,
>     it works,
>      > >> allowing inspection of all items.
>      > >>
>      > >> Any hints on what I may be doing wrong? The headers are all
>     accessible,
>     for
>      > >> instance. Should I build Qt with debug symbols enabled, as
>     recommended
>     for
>      > >> glibc?
>      > >>
>      > >> Using current Qt 4.8.5, Qt Creator 2.8.1, gdb 7.7.1, gcc 4.8.3
>      > >>
>      > >> Thanks!
>      > >> Francisco
>      > >
>      > > Try to print it from gdb cli, if it works you'll know the issue
>     QtCreator,
>      > > otherwise you're likely missing some symbols. You should always
>     compile
>     any
>      > > development libraries with debug symbols.
>      >
>      > You don't need debug symbols for inspecting containers. They are not
>      > needed. The only reason for enabling debug symbols in Qt is if
>     you want
>      > to step into Qt's code.
>
>     Thank you. You do need symbols though, just not Qts for this
>     specific case.
>     There are many reasons why you should compile your development
>     libraries with
>     symbols besides stepping into the code. Such as getting a backtrace.
>     Even
>     proprietary (closed-source) libraries often make the symbols
>     available for
>     this reason.




  reply	other threads:[~2015-03-24 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 13:07 [gentoo-user] [OFF TOPIC] Qt Creator unable to access containers in debug mode Francisco Ares
2015-03-24 13:52 ` [gentoo-user] " Nikos Chantziaras
2015-03-24 17:04   ` Francisco Ares
2015-03-24 19:12 ` [gentoo-user] " Fernando Rodriguez
2015-03-24 19:32   ` [gentoo-user] " Nikos Chantziaras
2015-03-24 20:07     ` Fernando Rodriguez
2015-03-24 20:43       ` Francisco Ares
2015-03-24 22:32         ` Nikos Chantziaras [this message]
2015-03-25  0:11           ` Fernando Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mesolu$oob$1@ger.gmane.org' \
    --to=realnc@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox