From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id ED224138CC5 for ; Tue, 24 Mar 2015 20:44:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 59C9FE090A; Tue, 24 Mar 2015 20:44:18 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2AAADE08F6 for ; Tue, 24 Mar 2015 20:44:17 +0000 (UTC) Received: by oigv203 with SMTP id v203so4480945oig.3 for ; Tue, 24 Mar 2015 13:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=qtkTrV3wfMKjdieByu/5cU4phTS3tmoucCO5HQVlYQs=; b=QktSx2SJb9Isrgj5gG651ICmHgxeMZLqr7snOhLyBYov1IIMNHLsRvyBRWx6LJlfOr MWCanwWZiUOTqmfi4y9V9f9F/UtiErAKgb6cMeMh8UpW0irQYQEVco9o9ygXvG/Uf9qR mO5hn5XS3Tu9i0GjS3Vf1+lhgzCBi83nws/VQNkSP9rDFBiQOsrJcPZvVD3F/v5txB4w tB6CAOe9q+IXGB85u90i9aK7GzqQD420k7wYBS5KVC9rxgdMWd12hsEdp3pAZyePaplF D9gHh6w7DJAOLm6NqR7vmyNH5JmVwjzEuCDD4vlOgvduXb0f7uextgK8v4pXmfgjavSx cN+Q== X-Received: by 10.60.69.229 with SMTP id h5mr4792793oeu.84.1427229856505; Tue, 24 Mar 2015 13:44:16 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.60.31.175 with HTTP; Tue, 24 Mar 2015 13:43:36 -0700 (PDT) In-Reply-To: <2443368.0jsocI3Rm7@navi> References: <1509173.AdsNnimB3Q@navi> <2443368.0jsocI3Rm7@navi> From: Francisco Ares Date: Tue, 24 Mar 2015 17:43:36 -0300 Message-ID: Subject: Re: [gentoo-user] Re: [OFF TOPIC] Qt Creator unable to access containers in debug mode To: gentoo-user Content-Type: multipart/alternative; boundary=001a11331d509c273305120ed863 X-Archives-Salt: c254936f-9749-4c6e-a30b-5b269977f5b2 X-Archives-Hash: ae6954a75ae96435dde247350cedbf4a --001a11331d509c273305120ed863 Content-Type: text/plain; charset=UTF-8 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>: > 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 in place of the expected item > quantity > > >> for a QList, for instance, but for a std::vector, 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. > > -- > Fernando Rodriguez > > --001a11331d509c273305120ed863 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you all for those clues, pretty interesting.
For now I suppose it is a gdb thing, as QtCreator is able to sh= ow details about STL containers as expected.

Going= to fiddle in gdb a bit more...


2015-03-24 17:07 GMT-03:00 Fernand= o Rodriguez <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.=C2=A0 It shows <not accessible> in place of the = expected item quantity
> >> for a QList, for instance, but for a std::vector<std::stri= ng>, it works,
> >> allowing inspection of all items.
> >>
> >> Any hints on what I may be doing wrong? The headers are all a= ccessible,
for
> >> instance. Should I build Qt with debug symbols enabled, as re= commended
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 iss= ue QtCreator,
> > otherwise you're likely missing some symbols. You should alwa= ys compile
any
> > development libraries with debug symbols.
>
> You don't need debug symbols for inspecting containers. They are n= ot
> needed. The only reason for enabling debug symbols in Qt is if you wan= t
> to step into Qt's code.

Thank you. You do need symbols though, just not Qts for this sp= ecific case.
There are many reasons why you should compile your development libraries wi= th
symbols besides stepping into the code. Such as getting a backtrace. Even proprietary (closed-source) libraries often make the symbols available for<= br> this reason.

--
Fernando Rodriguez


--001a11331d509c273305120ed863--