[Qt-creator] Qt data types and debugging

[Israel Brewster]

I was just  looking a bit closer at that gdbmacros.cpp file, and I  
noticed a comment at the top saying "we need 4.5 because of  
QLocalSocket use". Perhaps this is my whole problem?As I noted at the  
end of my first message, I am running 4.3.4 at the moment, so the if  
statement at the beginning is essentially completely excluding this  
file, even if I manually include it.

On Nov 7, 2008, at 9:33 AM, Andre Poenitz wrote:

> On Fri, Nov 07, 2008 at 08:36:31AM -0900, Israel Brewster wrote:
>> the value column was
>> blank, and I could not find a way to view the value.
>
> There is some text under "Welcome -> Getting started -> Debugging
> with Qt Creator"

Ah, yes. So I see. From that document, I find it says "To start using  
that feature, select Debug and Use Custom Display for Qt Objects".  
This option is already selected in the debug menu, but toggling it on  
and off doesn't appear to make any difference: QStrings still show no  
value, and QObjects still show up as pointers, which it would appear  
is not supposed to be the case.

>> Looking in the QtCreator preferences window, I find a section for
>> "Type Macros" under the debugger section, which points to a script
>> file at /Applications/QtCreator.app/Contents/Resources/gdb/qt4macros
>> that would appear (to my mind, at least) to deal with displaying
>> QStrings in the debugger.
>
> That's currently not used.

That answers that at least :)

>> The referenced script file, however, does
>> not appear to exist. The closest I could find was /Applications/
>> QtCreator.app/Contents/Resources/gdbmacros/gdbmacros.cpp, which is
>> obviously a C++ source file, not a script file.
>
> Right. That's compiled and linked together with your application
> and provides the necessary infrastructure to display the Qt types.
> This compilation and linking should happen automatically when
> Build&Run -> Build Settings -> Link Debugging Helper  is checked.
>
> If checking that box does not help, you could also add that file
> manually to the project yourself and used QT += network in the .pro
> file. That has basically the same effect.

That box was already checked, so I went ahead and added the file to my  
project. This resulted in the following two warnings during the build  
process, but otherwise no change:

Makefile.Debug:503: warning: overriding commands for target `debug/ 
gdbmacros.o'
Makefile.Debug:500: warning: ignoring old commands for target `debug/ 
gdbmacros.o'

Course, with that opening if statement in the file, I wouldn't really  
expect anything to happen :)

-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
> Andre'