date:20180716

Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

2018-07-16 Thread David Schulz

Hi,

I totally agree with you here, that was the reason for creating 
https://bugreports.qt.io/browse/QTBUG-67587. So if you both would leave a 
comment/vote on that report someone might look into this mess. 

> I don't think I remember ever having to do this with Visual Studio but 
I'll bite.

The change that introduced this behavior is relative new and would also effect 
a setup with visual studio, because the symbol files are also missing there. 
"offline installer would be too big with PDB files & we just can't create it" 
was the statement. BTW: The online installer is not affected by this.

Greetings David

-Original Message-
From: Qt-creator [mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org] 
On Behalf Of Michael Jackson
Sent: Monday, July 16, 2018 19:07
To: Bob Hood ; qt-creator@qt-project.org
Subject: Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

I ended up getting them installed (clunky way to install them) and then created 
a rule set in CMake to copy them to my local binary directory of the app that I 
am compiling.

Maybe instead of packaging them as a single archive of a single folder it would 
be better to create the proper sub-folders then create the archive. I had to 
individually select each .7z file for VS2017 and decompress them. Would be 
easier, I would think, to just be able to decompress the archive as it sites in 
Qt5.10.1/5.10.1 folder and everything gets put into the proper location.
--
Michael Jackson | Owner, President
  BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net 

On 7/14/18, 6:02 PM, "Bob Hood"  wrote:

Mine are in the Qt installation (the one that my Creator kit points to), in 
the bin\ folder, right along side the Qt5 .dll files.


On 7/13/2018 12:22 PM, Michael Jackson wrote:
> I don't think I remember ever having to do this with Visual Studio but 
I'll bite. So I downloaded the pdb zip file? I have Qt 5.10.1 with VS2017 x64. 
Where do I install the pdb files? My build dir? Or somewhere in the Qt5 
installation?
>
> Thanks
>
> --
> Michael Jackson | Owner, President
>BlueQuartz Software
> [e] mike.jack...@bluequartz.net
> [w] www.bluequartz.net 
>
> On 7/13/18, 12:38 PM, "Qt-creator on behalf of Bob Hood" 
 wrote:
>
>  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

Re: [Qt-creator] What's the crash?

2018-07-16 Thread Jason H

Yes!! I wonder why I don't get that anymore?


> Sent: Monday, July 16, 2018 at 10:37 AM
> From: "Nikos Chantziaras" 
> To: qt-creator@qt-project.org
> Subject: Re: [Qt-creator] What's the crash?
>
> Seems to be working fine here:
> 
>https://i.imgur.com/OfFSAk5.png
> 
> 
> On 16/07/18 17:05, Jason H wrote:
> > 
> >> There's nothing more the debugger or C++ can do for you here.
> > 
> > But it does at the command line:
> > Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
> > Process 79112 stopped
> > * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC 
> > (code=EXC_I386_DIV, subcode=0x0)
> >  frame #0: 0x00010fad a.out`main at main.c:7
> > 4   {
> > 5   int a = 2;
> > 6   int b = 0;
> > -> 7return a/b;
> > 
> > 
> > I'm pretty sure I remember some dialog appearing saying something about 
> > SIGSEGV (or in this case EXC_ARITHMETIC)?
> > 
> > MS gives this: 
> > https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
> > I thought earlier versions of QtC had something simular.
> > 
> > The difference is:
> > 
> > int *a, *b; *b=0;
> > return *a / *b;
> > 
> > Here, the problem could be that 'a' is out of process space, or 'b' is 0. 
> > If 'a' is a pointer, I don't necessarily know what my address range is. I 
> > have to deduce (and risk being wrong) what the actual crash was, meaning I 
> > could waste time going down the wrong path.
> > 
> 
> 
> ___
> 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

Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

2018-07-16 Thread Michael Jackson

I ended up getting them installed (clunky way to install them) and then created 
a rule set in CMake to copy them to my local binary directory of the app that I 
am compiling.

Maybe instead of packaging them as a single archive of a single folder it would 
be better to create the proper sub-folders then create the archive. I had to 
individually select each .7z file for VS2017 and decompress them. Would be 
easier, I would think, to just be able to decompress the archive as it sites in 
Qt5.10.1/5.10.1 folder and everything gets put into the proper location.
--
Michael Jackson | Owner, President
  BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net 

On 7/14/18, 6:02 PM, "Bob Hood"  wrote:

Mine are in the Qt installation (the one that my Creator kit points to), in 
the bin\ folder, right along side the Qt5 .dll files.


On 7/13/2018 12:22 PM, Michael Jackson wrote:
> I don't think I remember ever having to do this with Visual Studio but 
I'll bite. So I downloaded the pdb zip file? I have Qt 5.10.1 with VS2017 x64. 
Where do I install the pdb files? My build dir? Or somewhere in the Qt5 
installation?
>
> Thanks
>
> --
> Michael Jackson | Owner, President
>BlueQuartz Software
> [e] mike.jack...@bluequartz.net
> [w] www.bluequartz.net 
>
> On 7/13/18, 12:38 PM, "Qt-creator on behalf of Bob Hood" 
 wrote:
>
>  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" 
 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 QStri

Re: [Qt-creator] What's the crash?

2018-07-16 Thread André Hartmann


Hi Jason,


There's nothing more the debugger or C++ can do for you here.

My comment refered to something like this in your code:

QList data;
data[0] = 123;

That will crash in qlist.cpp with index out of range, and not in your 
code. Therefore it is not immediately obvious what causes the crash. But 
with the stack trace you can find the guilty function.


It's up to you to inspect the stack though. If global variables are 
involved, things might get more complicated.


> MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png

> I thought earlier versions of QtC had something simular.

Are you working with a debug version of your program?

Regards,
André


But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC 
(code=EXC_I386_DIV, subcode=0x0)
 frame #0: 0x00010fad a.out`main at main.c:7
4   {
5   int a = 2;
6   int b = 0;
-> 7 return a/b;


I'm pretty sure I remember some dialog appearing saying something about SIGSEGV 
(or in this case EXC_ARITHMETIC)?

MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
I thought earlier versions of QtC had something simular.

The difference is:

int *a, *b; *b=0;
return *a / *b;

Here, the problem could be that 'a' is out of process space, or 'b' is 0. If 
'a' is a pointer, I don't necessarily know what my address range is. I have to 
deduce (and risk being wrong) what the actual crash was, meaning I could waste 
time going down the wrong path.
___
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

Re: [Qt-creator] What's the crash?

2018-07-16 Thread Andy

FWIW I do (sometimes?) get a dialog like Nikos (MSVC 2017):

[image: 2018-07-16 10_29_04-Exception Triggered.jpg]

(What's "The inferior"?)

Once that's dismissed, however, the only place I can find the info is
digging through the debugger log.

It would be useful to indicate in the thread menu which thread crashed
along with the reason. Maybe add to the menu entry:

  "#0 - crashed (division by zero)"

or something like that.

---
Andy Maloney  //  https://asmaloney.com
twitter ~ @asmaloney 



On Mon, Jul 16, 2018 at 10:37 AM Nikos Chantziaras  wrote:

> Seems to be working fine here:
>
>https://i.imgur.com/OfFSAk5.png
>
>
> On 16/07/18 17:05, Jason H wrote:
> >
> >> There's nothing more the debugger or C++ can do for you here.
> >
> > But it does at the command line:
> > Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
> > Process 79112 stopped
> > * thread #1, queue = 'com.apple.main-thread', stop reason =
> EXC_ARITHMETIC (code=EXC_I386_DIV, subcode=0x0)
> >  frame #0: 0x00010fad a.out`main at main.c:7
> > 4 {
> > 5 int a = 2;
> > 6 int b = 0;
> > -> 7  return a/b;
> >
> >
> > I'm pretty sure I remember some dialog appearing saying something about
> SIGSEGV (or in this case EXC_ARITHMETIC)?
> >
> > MS gives this:
> https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
> > I thought earlier versions of QtC had something simular.
> >
> > The difference is:
> >
> > int *a, *b; *b=0;
> > return *a / *b;
> >
> > Here, the problem could be that 'a' is out of process space, or 'b' is
> 0. If 'a' is a pointer, I don't necessarily know what my address range is.
> I have to deduce (and risk being wrong) what the actual crash was, meaning
> I could waste time going down the wrong path.
> >
>
>
> ___
> 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

Re: [Qt-creator] What's the crash?

2018-07-16 Thread Nikos Chantziaras


Seems to be working fine here:

  https://i.imgur.com/OfFSAk5.png


On 16/07/18 17:05, Jason H wrote:



There's nothing more the debugger or C++ can do for you here.


But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC 
(code=EXC_I386_DIV, subcode=0x0)
 frame #0: 0x00010fad a.out`main at main.c:7
4   {
5   int a = 2;
6   int b = 0;
-> 7 return a/b;


I'm pretty sure I remember some dialog appearing saying something about SIGSEGV 
(or in this case EXC_ARITHMETIC)?

MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
I thought earlier versions of QtC had something simular.

The difference is:

int *a, *b; *b=0;
return *a / *b;

Here, the problem could be that 'a' is out of process space, or 'b' is 0. If 
'a' is a pointer, I don't necessarily know what my address range is. I have to 
deduce (and risk being wrong) what the actual crash was, meaning I could waste 
time going down the wrong path.




___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] What's the crash?

2018-07-16 Thread Jason H



> There's nothing more the debugger or C++ can do for you here. 

But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC 
(code=EXC_I386_DIV, subcode=0x0)
frame #0: 0x00010fad a.out`main at main.c:7
   4{
   5int a = 2;
   6int b = 0;
-> 7return a/b;


I'm pretty sure I remember some dialog appearing saying something about SIGSEGV 
(or in this case EXC_ARITHMETIC)? 

MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
I thought earlier versions of QtC had something simular.

The difference is:

int *a, *b; *b=0;
return *a / *b;

Here, the problem could be that 'a' is out of process space, or 'b' is 0. If 
'a' is a pointer, I don't necessarily know what my address range is. I have to 
deduce (and risk being wrong) what the actual crash was, meaning I could waste 
time going down the wrong path.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

2018-07-16 Thread Tino Pyssysalo

Hi all,

In March this year, I requested a repo for an open source telemetry plugin for 
Qt Creator. Now, the plugin has been implemented and I’d like to request two 
repos:

  *   A repo for a Connected Creator plugin
  *   A playground repo for a telemetry library



Description: The Qt Company wants to collect usage data from Qt development 
tools. For that purpose, we have developed a general-purpose telemetry library 
and a Qt Creator -specific plugin, using the telemetry library. The reason to 
collect the data from our users is to learn, how developers use Qt Creator and 
other tools, how usage patterns change, how quickly new features and versions 
are started to be used, which tools are mostly used? This information is one 
data source, helping us to make decisions, how to further develop our products. 
In the short run, we believe we will get valuable information, how to improve 
the user experience of our products.



The connected creator plugin implements the frontend for tracking the data from 
different data sources in Qt Creator. The frontend consists of a simple UI to 
enable/disable the plugin, to set logs expiration period, and to view the data 
to be transmitted or previously transmitted data (logs). Currently, the plugin 
tracks Qt Quick Designer usage only: launch count and usage time. General 
platform data is collected by the telemetry library. This data currently 
includes compiler details, locale, OpenGL type and version, Qt version, screen 
details, Qt Creator version, license type (evaluation, commercial, no license), 
and unique id (generated with QUuid).



All collected data is anonymous. No personal data such as project names, 
project locations and paths, IP or MAC addresses, email addresses or Qt Account 
details are collected.



The data is stored in the backend server, owned by The Qt Company. The backend 
is complexly separated from the telemetry frontend and the code will be 
provided in The Qt Company private repo: 
https://github.com/TheQtCompany/qt-telemetry-backend.



The collected data is cached into a settings file before the transmission. This 
allows the user to check, what data is going to be transmitted and even disable 
the plugin before any data is actually transmitted. In addition, data caching 
allows calculating key values in the frontend instead of sending each user 
event to the server separately. This reduces the network traffic significantly. 
By default, the cached data is transmitted to the server once per week. It is 
possible to log the transmitted data into the files to verify all the data 
transmitted to the server.



The plugin is planned to be completely opt-in. The online installer will ask 
the user, if he/she wants to install the plugin. There is no default selection 
for the installation, but user must explicitly choose either to install or not 
install the plugin. If the user decides to install the plugin, it can be 
disabled in Qt Creator settings. The user is able to see the cached data and 
before the first transmission, the user can disable the plugin, even though it 
has been installed.



More implementation details can be found in Jira ticket: 
https://bugreports.qt.io/browse/QTCREATORBUG-20250



Existing repos:

Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin

Telemetry library: https://github.com/akontsevich/QTelemetry



Responsible: Tino Pyssysalo



Requested repos:

Connected Creator plugin: qt-cresator/plugin-connectedcreator

Telemetry library: playground/telemetry

---
Tino Pyssysalo
Senior Manager
Product Management

The Qt Company
tino.pyssys...@qt.io
http://qt.io

The future is Written with Qt
---




___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

Re: [Qt-creator] What's the crash?

Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

Re: [Qt-creator] What's the crash?

Re: [Qt-creator] What's the crash?

Re: [Qt-creator] What's the crash?

Re: [Qt-creator] What's the crash?

[Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

8 matches

Site Navigation

Mail list logo

Footer information