[Qt-creator] Problems with CDB Integration

[Friedemann Kleint]

Hi,

> > The compiled program just runs fine outside qtcreator - or not really
> > fine that why I need a debugger working -

But can you start it from Qt Creator by hitting the "Run" button? The question 
is, is the run configuration (Project mode/run configuration) sufficient to start 
the application, does it see the right paths to your DLLs, etc.

> > When hitting the "start debug" button a message with four options pops
> > up, stating something with the debug helper that cannot be found or
> > started. 

That box should have a "Details" button, which will show more information.

> > Then it directs me to the debugger properties where I can
> > recompile the debugging helper (as I understand for gdb, which is not
> > what I want, as I need the cdb to work).

Those depend on the Qt version used; they will work for CDB as well.

> > ------------------------ these messages seem to be related to
> > misconfigured debugging symbols directory:
> >
> > *** wait with pending attach
> >
> >  Symbol search path is:
> >  *** Invalid ***

The symbol search path can be configured in the CDB settings, however, this 
warning is not to be taken too seriously. (the "Insert" dropdown menu has an 
option to add the Microsoft Symbol server for the operating system library 
symbols. It requires specifying a local cache directory.)

> > Four projects use the app template. The odd thing: the way I have set it
> > up it seems not to push changes from the source files all the way down to
> > the __program_.exe only to the last __program_.lib then it stops. Also,
> > jom and nmake all the same run through all the subdirs until it reaches
> > the point of change which takes quite some time. Only if I delete the exe
> > file, the final linking is invoked.
> >
> > What might I be doing wrong, maybe do I need to specify all the
> > dependencies? How? It seems that the missing exe is pulling down the
> > making of libs, obj and cpp. But shouldn't it be the other way round that
> > a change in a cpp pushes all the way down to the related .exes?
> >
> > To wrap it up: I cannot tell if the debugging problem is somehow related
> > to a misconfigured qmake setup with all the projects, as the debugger
> > crashes/exits with invalid symbol search path.

Then  it looks like the application is not properly built. Off the top of my 
head, specifying the DEPENDPATH qmake variable to contain the include path of 
the application ( http://qt.nokia.com/doc/4.5/qmake-variable-
reference.html#dependpath ) might help. It will then detect changes of the 
library header files and recompile accordingly.

Regards,
Friedemann

-- 
Friedemann Kleint
Nokia, Qt Development Frameworks