I've recently started using Qt with Intel's latest compiler in the Eclipse IDE (Linux 64-bit).
All is well, apart from one glitch.
Building and running Qt applications works fine in Eclipse (supported by Intel's and Qt's plugins), but when I come to debug graphical applications (usingIntel plugin)I get the following in the Console window as soon as I create a QApplication class in main() and my app terminates:
cannot connect to X server :0.0
I'm using idbc - Intel's debugger as suggested in the documentation:
Use "Standard Create Process Launcher"
and select "Intel Debugger" in the debugger tab.
This works fine for non-graphical apps.
I know the error is a standard Qt error complaining it can't spawn a connection to X to draw the application on the screen. But :0.0 does indeed exist and I've even tried disabling X authentication in case Eclipse is spawning it in a weird and wonderful way.... no dice. Modifying the DISPLAY environment variable changes the error to report the address I set it to, so it appears it is picking up the right environment.
Determined to use this setup (everything else is nice, after all), I've found if I pass into my app as parametersthe Qt specific override "-display :0.0" then it can at least spawn the GUI, but I get warnings:
QGtkStyle was unable to detect the current GTK+ theme.
_IceTransOpen: Unable to find transport for local
Qt: Session management error: None of the authentication protocols specified are supported
And my app is displayed looking pretty ugly with not theme at all applied.
I can live with this - providing no other problem occur, but it seems like a trivial problem - The Eclipse IDB plugin is spawning the app in a way which is stopping it behaving as would inside a normal terminal window. Running idbc on my app from a separate terminal using exactly the same command as I can see Eclipse is using, works fine *IF* I remove the -tty switch:
/opt/intel/composerxe-2011.0.084/bin/intel64/idbc -gdb -q -nw -i mi -tty /dev/pts/9 --cd=/home/phil/dev/c++/workspace/AddressBook --nx /home/phil/dev/c++/workspace/AddressBook/AddressBook
...and none of this occurs using GDB, where the GUI pops up just fine.
I'm out of ideas - does anyone have any suggestions how to rectify this?
Fedora 14, 64bit with the following environment:
Eclipse 3.5.2, 64 bit
Java 1.6, 64 bit
IDB CDT Plug-in 6.0.0
and of course the latest IDB 12.0
Since it works on our end, there must be somethign specific to your setup. Can you give us a list of all the relevant components in your software stack similar to what I just listed? Are we missing something else in your setup perhaps?