qt5/qtcreator in ubuntu Precise under Windows 8.1 host

[devvy77]

Hello,

Its impossible, for some reason to run and debug any qt5 application (even the simplest qt5 widgets app) in VirtualBox if using Ubuntu 12.04 under Windows 8.1

The reason for this is that gdb seems to throw a wobbly when debugging -- upon exiting the app being debugged, there is a message that says something like:

cannot find user-level thread for LWP xxxx :generic error

Where xxxx is some apparently random number (in this case it was 1953 -- the next time I ran it, it was 2004)

Then, you have to use the qtcreator "stop debugging" menu item TWICE, and on the second attempt it says:

"Unexpected GDB Exit"

If you don't do this, the virtual machine consumes 100% cpu and the host becomes difficult to use.

NOTE: using qt4, this doesn't happen. I double-checked on my dual boot system, and on my laptop, booting into Ubuntu natively, and I cannot re-create the bug -- so although one could argue its a qt5 bug (since qt4 apps run correctly), its definitely something realted to virtualbox also.

It does it in a clean install of Ubuntu 12.04 either 64 or 32-bit under my Windows 8.1 host.

Steps to reproduce:

1) Install virtualBox on Windows 8.1 2) Install Ubuntu 12.04 LTS in the virtualBox. 3) Piddle about installing guest additions and enabling 3D, so Unity doesn't run like a pig:

​http://www.typicaltips.com/2013/02/ubuntu-lags-in-virtualbox-solution.html

4) Install qtcreator and qt5 from: ​http://download.qt-project.org/official_releases/online_installers/1.5/qt-linux-opensource-1.5.0-x86-online.run

5) Start qtCreator.

6) Create new Project: a simple (empty) qt5 widgets project

7) Run the project (IN DEBUG MODE) and observe, 9 times out of ten, the error I describe (it doesn't happen EVERY time!). Note the error manifests right as you close the qt mainwindow, i.e. as the program exits.

[Frank Mehnert]

Please attach a VBox.log file of such a VM session.

[devvy77]

Requested Log File

[devvy77]

Noted also that one time, it segfaulted somewhere deep inside pthreads... hope that is useful info.

Should also be noted that this VBox suffers from the USB sound card bug that means i have to unplug the audio device before vboxserver will start and not consume 100% cpu -- but lets not worry about that right now...

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.