[SOLVED] Ubuntu 12.04 QtCreator 2.5 QT5 Build Debug Tools Chains auto-detect

Skylar

Hello,

Ubuntu 12.04 : fresh upgrade from 11.10
QtCreator 2.5 out of the box install
QT5 trunk compiled yesterday in -developper-build without installation

When trying the debug mode I get :

The debugger engine 'LLDB engine' is disabled.
There is no gdb binary available for binaries in format 'x86-linux-generic-elf-64bit'

My gdb config tell me :
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
This GDB was configured as "x86_64-linux-gnu".

Can you please help me to setup the debugger correctly ?

Need I to change the Gbd (how?), need I to change QTCreator (how ?) ?

Regards,
Skylar

tobias.hunger

Please check the debugger settings in the tool chains defined in Tools->Options->Build & Run->Tool chains. Do they point to the right place?

Skylar

Thank you,

I'm testing but I can only select : elf, match_o, pe, qml_rt, unknown

I will investigate this point if some can match the “x86_64-linux-gnu”

tobias.hunger

Don't mess with the ABI if you don't know exactly what you are doing! Changing that will cause creator to not build using that tool chain, which is most likely not what you want:-)

There should be a debugger setting in those tool chains, please check that one.

Skylar

Tahnk you, I will give a try of them.

I checked the debugger docs but wel I'm a bit lost.

I wil continue the investigation about the message with the options.

Skylar

Well on the Build&Run tool I can't find any of the options that change the point.

The debugger engine 'LLDB engine' is disabled.
There is no gdb binary available for binaries in format 'x86-linux-generic-elf-64bit'

Gdb I have but no LLDB installed but it tell 'disabled'
Gdb is found in the path.

On the Tools chains the auto-detected is Clang installed from a ppa not manually build.
But' is compilling.

Only the Qt Versions is a Manual one pointing to Qt5 local build.
There is the warning with the 'No qmlviewer installed.' but qmlscene is working from the path.

Skylar

Reinstalled QT Creator, clang, llvm from a backport but still have this error.

I miss somewhere in the path but can't find any clue where.

Is there a way o make my QT5 build autodetected too ?

Can be linked maybe : qmake -v
QMake version 2.01a
Using Qt version 4.8.1 in /usr/lib/x86_64-linux-gnu

and not the qmake one in the QT5 build.
But qmlscene working from the QT5 build path

tobias.hunger

Go to Tools->Options->Build & Run->Tool chains and select the tool chain you are using. That should open some details on that tool chain. These details should contain the path to the debugger that is going to be used. Debugger settings are per-tool chain, so you need to make sure to set up the one you actually are using.

You will want to use gdb. LLDB is not really stable anywhere but on mac (at least that was the state when I tried it the last time).

Skylar

Thank you Tobias for your help:

I'm really bad.

Under the autodetected Tools Chains none have a debugger entry line.
Nor the Clang32 bit nor the Clang 64bit.

Skylar

Thank you Tobais,

I was looking too far in the wrong direction.

Message :
The debugger engine ‘LLDB engine’ is disabled.
There is no gdb binary available for binaries in format ‘x86-linux-generic-elf-64bit’

My gdb config tell me :
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
This GDB was configured as “x86_64-linux-gnu”.

Solution :
Go to Tools->Options->Build & Run->Tool chains
Check the auto-detected chain you are using and look the Debugger path.
If empty, Clone the the entry and add the path to your debugger by default the /usr/bin/gdb

Nice to have :
Can it be done by the autotection setup of tool chains ?
Or have a button to ask a new auto-detection.

tobias.hunger

Creator 2.6 has this changed quite a bit: The debugger becomes part of the target there.

Skylar

Thank you, is there a way to get QtCreator 2.6 and build it against latest QT5 trunk already ?

tobias.hunger

You can grab the sources of Qt Creator from our repos. It should build against Qt5.

Skylar

Good news I start the process.

And...thank you for this and for QT.