Running a simple program
Qt Code:
  1. int main(int argc, char **argv) {
  2. QApplication myApp(argc, argv);
  3. }
To copy to clipboard, switch view to plain text mode 
built with qmake CONFIG += debug runs under gdb and after the only statement
Qt Code:
  1. gdb> p myApp
To copy to clipboard, switch view to plain text mode 
prints all the normal info about a QApplication object. So I think debug libraries etc. are all in place and properly configured.

In a more complex program stopping after the QApplication creation gdb is only prepared to report
Qt Code:
  1. (gdb) p myApp
  2. $3 = <incomplete type>
To copy to clipboard, switch view to plain text mode 
and debugging properties or methods of Qt objects fails although the program compiles, links and executes properly except for one or two functions.

Could any of the following upset gdb:
1. Linking with a plain C objects from another directory
2. Linking with libtiff and/or libusb-1.0
3. Using a number of struct rather than classes
I think all these are acceptable but any ideas as to what upsets gdb are welcome.

PS. I could pare down my program until gdb starts working but that is very timeconsuming because of all interrelationsships. Would love a simpler list of things to try.

All suggestions welcome.
Enno.