Ah! That was indeed the problem (and hopefully Micheal's as well). My debug\
folder had Qt5 DLLs sitting in it, because I mistakenly assumed they had to be
there in order for debugging to work. When I deleted them, Creator used the
kit path, and found the *.pdb file it needed. I can now see QStrings.
This was pilot error. Creator was not at fault. Sorry for the noise.
On 7/12/2018 11:12 PM, David Schulz wrote:
Hi,
cdb can't find the pdb file for
W:\Dev\Personal\Projects\Qt\Skoop\client\debug\Qt5Cored.dll. Do you know where
that file is on your hard disk?
And please create a bug report for this issue, so we can move the discussion
to jira.
Greetings
David
-----Original Message-----
From: Qt-creator [mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org]
On Behalf Of Bob Hood
Sent: Friday, July 13, 2018 04:30
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?
https://pastebin.com/z2eZxVuu
On 7/9/2018 5:10 AM, David Schulz wrote:
Hi,
I've checked 4.6.2 and 4.7 with a Qt based on msvc 2017 WindowsSDKVersion
10.0.17134.0 and I get sensible dumper values in the locals and expression view.
Can you share the content of the debugger log (Window > Views > Debugger Log)
on your codepaster of choice?
Greetings
David
-----Original Message-----
From: Qt-creator [mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org]
On Behalf Of Bob Hood
Sent: Saturday, July 7, 2018 15:36
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?
So only Michael and I are experiencing this? Or is that only Michael and I are
using 4.6.2 on Windows?
On 7/6/2018 6:08 AM, Michael Jackson wrote:
I also just happened to setup QtCreator 4.6.2 and I had the same issue. Latest
VS2017 release running on Windows 10 x64.
--
Michael Jackson | Owner, President
BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net
On 7/5/18, 6:49 PM, "Qt-creator on behalf of Bob Hood"
<qt-creator-bounces+mike.jackson=bluequartz....@qt-project.org on behalf of
bho...@comcast.net> wrote:
I have installed Creator 4.6.2 (normally, I use 4.0.3) and have started
a new
project with it. Prior to installing it, I already had Visual Studio
2017
15.4.7 installed, along with Windows SDK v10.1.17134.12 with "Debugging
Tools
for Windows". Creator 4.6.2 automatically found the debugging tools,
and I
reconfigured my Kits accordingly for use with Qt 5.9.4 Desktop (which I
built
myself using Visual Studio 2017, so they are ABI compatible).
I'm debugging into my Qt application, and I'm getting "not accessible" the
Locals pane for QString and QStringList. Was there some further set-up I
needed to perform? I don't recall having this issue with 4.0.3.
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
