Qt 5.4 Qt creator 3.3 debugging problem

gametack

I just installed Qt 5.4 with Qt creator 3.3 and MinGW 4.9.1 and everything worked fine until i tried to debug my qml project. I keep getting this error;

"The slave debugging engine required for combines QML/C++-Debugging could not be created: Unable to create a debugger engine of the type "No engine"

Can anyone help me.
Thanks in advance

burtek

I'm having the same problem, newest QT creator seems to be incompatible with the newest MinGW (and the newest QT itself). All we can do is downgrade to qt 5.3 and wait for QT Creator update

gametack

I tried to use the gdb from MinGW 4.8 and it works, so i guess that's an optino for now.

gyll

Did you guys file a bug report about this? if not, please do so at http://bugreports.qt-project.org/

burtek

https://bugreports.qt-project.org/browse/QTCREATORBUG-13679

Also there is a workaround given there

koahnig

[quote author="gametack" date="1418519784"]I tried to use the gdb from MinGW 4.8 and it works, so i guess that's an optino for now.[/quote]

That is nothing new, When installing Qt 5.3.1 with Qt creator at that time, I was facing similar issues. It depends apparently whether gdb is detected automatically or not.

AFAIK you can use only gdb with MinGW.

burtek

[quote author="koahnig" date="1418559405"]

That is nothing new, When installing Qt 5.3.1 with Qt creator at that time, I was facing similar issues. It depends apparently whether gdb is detected automatically or not.

[/quote]

According to the bug report I linked to in previous post they already have patched this bug, but the patch hasn't reached the online repositories yet, since it was last-minute fix. It's going to go online as soon as possible

koahnig

[quote author="burtek" date="1418564490"]
[quote author="koahnig" date="1418559405"]

That is nothing new, When installing Qt 5.3.1 with Qt creator at that time, I was facing similar issues. It depends apparently whether gdb is detected automatically or not.

[/quote]

According to the bug report I linked to in previous post they already have patched this bug, but the patch hasn't reached the online repositories yet, since it was last-minute fix. It's going to go online as soon as possible[/quote]

Yes, I have checked the bug report after post above.

For sure I did not have to do such patching as described in the bug report.
The autodetection issue has been around for quite a while.