On 01/04/2012 08:27 PM, André Pönitz wrote: > Dear Nenad Lecek, > > on Wed, Dec 28, 2011 at 03:24:57PM +0000, you wrote: >> Qtcreator 2.4.0 (Ubuntu 11.10, 64 bit) has one embarrassing bug (F10 didn't >> work). Pretty much basic issue. > This might be caused by your desktop environment using F10 for its own > purposes. > > Asking google for "ubuntu 11.10 F10" brings up quite a few applications > with exactly the same (using your words) "embarassing bug" > > It even brings up things like > > "[configure] F10 key binding under “Ubuntu Unity Plugin / Behaviour / > Key to open the first panel menu” to something else (I used F12)." > > or > > http://askubuntu.com/questions/29553/how-can-i-configure-unity > > > If that is your problem, you are barking up the wrong tree here. Have to admit that I was not aware that Unity uses F10 and the problem I have is a side-effect caused by Unity. In mean time I switched back to Gnome desktop (being disappointed with Unity look&feel, global menu, etc.) and the problem with F10 is gone. So thank you pointing me to the root cause. It is really strange decision that desktop environment uses one such frequently used key by applications. But this comment is for Unity, so sorry for incorrectly blaming qtcreator. Another problem with debugger crash at startup, happens with 2.4.81 but not with official qtcreator2.4.0. Therefore, I'm using again qtcreator 2.4.0.
> > Keystrokes eaten by the window manager are not delivered to Qt Creator > (or any other application for that matter) so Qt Creator (or any other > application for that matter) can obviously not react to it. > >> Doesn't make much sense to announce C++ IDE if >> key shortcut for basic debugging step doesn't work. How that could happen is >> really surprising, anybody tested it ever on Linuxes? > Rest assured that quite a few people do use Qt Creator on Linux. > >> Even if the problem is not inside qtcreator, some workaround should be >> clearly suggested with some link together with installation steps so >> that this is not a show-stopper. > There is no way to tell which key strokes are _not_ delivered to an > application. If a user decides to use any given desktop environment he > accepts some of the decisions taken by this environment and/or agrees > that the ways to override those decisions are sufficient for him. My proposal for improvement here would be to provide more detailed info about known issues, somewhere with Qtcreator installation notes. E.g. in chapter like "Getting started with qtcreator" could be helpful to find a list of known issues per distro (e.g. known issue on Ubuntu - F10 clash with Unity and the link to the solution). This would save me a lot of time. Instead of taking later (unstable and unofficial) version of qtcreator, simple fix for the shortcut clash with the Unity will do. > > In this particular case it seems that both Qt Creator _and_ the DE > can be configured to avoid the shortcut clash, but there's no (sensible) > way to avoid it in advance. Important is to know that the shortcut clash is the reason for such problem. Then is much easier to find the solution. > >> [...] You may find small example bellow, for which isn't possible to >> run the application in debug mode to reach breakpoint. The qtcreator >> was started with root credentials, and is the same if is started with >> normal user credentials. The break point was set where >> QCoreApplication instance is instantiated. > According to this log there is no attempt to set any breakpoint, so to > me it pretty much looks like you did not specify any. The breakpoint was specified and the problem was that debugger crashed before it came to the breakpoint. Since, this version of qtcreator (2.4.81) is not officially released, this is still lets say ok for work in progress. Following other comments saying 2.4.81 is not official version I went back and installed again qtcreator 2.4.0 from installation file: http://qt.nokia.com/downloads/qt-creator-binary-for-linux-x11-64-bit (not from source). Interestingly enough, with qtcreator2.4.0 debugger doesn't crash before reaching the breakpoint. Debugging works again, breakpoint could be reached. This is fine with me again, I'm generally happy with official version of qtcreator. The confict with Unity is resolved and debugger crash is gone by switching to official qtcreator 2.4.0. I believe that developers actively working on qtcreator will fix the problem I had with debugger crash in qtcreator 2.4.81 and later official version of qtcreator will have stable debugger. Thanks to all who provided comments and helped to resolve the problem. Best regards Nenad > > Can you please confirm you set any, and also that there is nothing > unsual in your .gdbinit? A screenshot of your "Breakpoints" view would > help a lot. Please refer to description above. > > Thanks. > > Andre' > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
