I recently installed Ubuntu 18.04 LTS, for the Windows Subsystem For Linux (WSL).
I installed a large number of packages, including ubuntu-desktop, build-essential, qtcreator and a number of others.
QTCreator itself seems to work fine for the most part. I can compile projects and run them in both Debug and Release just fine.
However, when I try to enter "Start Debugging" in a debug release, it hangs indefinitely. Once started, "stop debugging" does not work anymore, and the only fix is to completely kill QTCreator and restart it. Same thing happens on a coworkers machine.
Is this a known limitation of WSL?
Emacs + GDB seems to fine for debugging, so it shouldn't be an issue with GDB which I believe QTCreator uses under the hood. (Though for various reasons, I still want QTCreator's debugger specifically)
Ubuntu 18.04 LTS
GDB is version (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Windows 10 is build 1909
QTCreator is version 4.5.2, based on QT 5.9.5
Using VcXsrv Windows X Server
Related
QTCreator version: 4.11.0
Based on Qt 5.12.8
OS: Ubuntu 20.04 on WSL 1
I have a test suite using the QTestFramework which is driving a C++ dynamic library to test it.
Running the debug release normally is perfectly fine
For running the debugger:
If I try chose the "Run in Terminal" option, the program seems to hang forever
If I don't chose "Run in Terminal", it runs fine, but never hits breakpoints
I have tried to set breakpoints both in the test program as well as the library itself, but none are ever hit.
Both the test suite and library are being built in debug mode, not release.
I've installed pocl on Ubuntu VMware and it works.
But there is nothing how to integrate into my CMake project.
Has anybody experience?
Everything is fine on Windows, because I could install CUDA.
On Ubuntu, installataiton works:
I'm using a script to build Windows and Linux versions (from Windows). Linux build is done by sshing to Linux VM and running CMake build. Sources are located on Windows folder shared with Ubuntu VM.
CMake does full rebuild everytime, even if there's no changes since the last build. I suppose the problem is that CMake (or GCC?) doesn't get or reads incorrectly Windows NTFS timestamps.
Is there any cure for this?
CMake 3.7.1, GCC 4.9, Windows 10, Ubuntu 16.04 LTS, VirtualBox 5.1
I build GDB for ARM from GDDBSources(GDB7.5) using MinGW and MSYS for windows.But sometimes while connecting GDB to the QEMU , GDB crash occurs with a message :
"gdb.exe has stopped working" in windows7.
What is the solution of this issue?
I had the same situation before. The solution is using mingw-w64 in place of MinGW in windows 7. It works well for me.
I have recently started using VirtualBox to get my Linux environment rather than fully using Ubuntu. For me this works well. But recently i have realized that in the Ubuntu vm the only thing I use a lot is the terminal, mostly just because I need the Linux environment and not the full desktop.
So I tried installing Ubuntu server into a VM, which worked. But as soon as I reboot the machine, it fails after the system boot logo. After BIOS and where I would log on from the command line I simply get a black screen with a non blinking cursor. So I am never fully able to boot into the vbox.
I read up on the command line version, trying to run it headless and then connecting to it from demote desktop. after starting the vbox I am able to connect to the desktop and see the grub screen but after selecting Ubuntu I get that same non-blinking cursor.
So is this really possible? I tried cygwin but it never really felt adequate to me. I like and am very comfortable with the Ubuntu/Debian command line. How could I (if possible) accomplish this? I want to be bale to start up the VBox and get the full command line for that vbox session. Any ideas?
Ubuntu version: 10.10, VirtualBox v. 4.0.4 r70112 and I am on Windows 7 Ultimate.
You didn't mention the versions of Ubuntu and Virtualbox.
I failed twice to install full Ubuntu 10.10 over the latest VirtualBox 4.0.4 over Ubuntu (problems like those you describe), so I switched to Debian 6.0.
All you require to install Ubuntu headless is to install the server version, which you already did. If you get blank screens, tweak the ioapic settings in both VB and Ubuntu. Another tweak is to switch between IDE and SATA drivers for the main disk (the Grub in my non-virtualized Ubuntu hangs if there's USB media attached at boot time).
If you can run full Ubuntu on a VM, you can try downgrading it by removing the xserver-xorg package, or changing the default runlevel.
If all you want is a Linux consule, you can install Debian 6 without any GUI components.