Qtcreator fails to run and generates core (SIGILL)
-
Just saw this during a tea break. I work from home, so I whizzed across to my home machine and tried it. Doh! Still no go.
I'll look at playing with compilation this weekend. I might bite the bullet and try a full installation instead of using the *.run package. I'll report back when I've finished.
-
Interesting goose chase, it should be possible to narrow down. One way to fix a working 32-bit flavoured Qt is if you install VirtualBox on your 64-bit modern PC, and in that VirtualBox install a 32-bit Fedora and 32-bit Qt 5.2.1. That should enable you to compile and copy executable files into the "steam" machine.
Also you can try another (simple :-) test to conquer that welcome screen: if you have an SSH server installed on the old machine, you could try ssh:ing in with the -X switch to remotely run QtCreator.
-
Hi,
You can also try to disable the welcome plugin (in About plugins)
Hope it helps
-
I'll try the Virtualbox thing as a first step. I'll install Fedora 20 i686 and then the qt-opensource-linux-x86-5.2.1.run package so I have the same situation as on the old machines. If it works on the virtual machine, it must be h/w related.
How do i disable the welcome plugin?
-
Go to "About Plugins" in the help menu IIRC, look for the welcome plugin (around the end of the list) and there you can disable it
-
Disabling the welcome plugin is an excellent idea (I tried by removing the help DLL, QtCreator wasn't pleased). But in this case, when QtCreator dies after 2 seconds I think, you have to be world's fastest mouse clicker to be able to reach the help menu :-)
Anyway, disabling the welcome plugin should change a .conf file for QtCreator somewhere. So another way of disabling the plugin is to edit the .conf file.
-
Found it, on my Debian it's in /home/henry/.config/QtProject/QtCreator.ini.
Locate the [plugins] section, change
@Ignored=@Invalid()@to
@Ignored=Welcome@BTW, this is a very good thing to do for WinXP and Win2k3 users running QtCreator 5.2.1, because on those systems the welcome screen doesn't refresh properly (leaving artifacts on the screen).
(Perhaps QtCreator needs a command line switch for this, i.e. start in "safe" mode, or allow you to specify what plugins are to be ignored.)
-
That one is already available:
-noload <plugin>The rest of the list can be found "here":http://doc-snapshot.qt-project.org/qtcreator-3.0/creator-cli.html
-
Aha, thanks! Of course, should've guessed there is a --noload option already in there. (Great minds think alike :-)
Looking at the list now and discovered a gem: -lastsession
This is basically the only thing I've missed when using QtCreator, e.g. when I want to exit QtCreator, sync with GitHub and resume coding, that switch is perfect.I've just recently discovered Qt (a couple of months) since spending more than 20 years with Visual Studio, but I'm already regretting why I didn't switch sooner!
-
Well, when I got my Virtualbox machine configured, it works!!!
The difference I can see is the cpuinfo
==================================
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
stepping : 7
cpu MHz : 3563.966
cache size : 6144 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 rdtscp constant_tsc pni monitor ssse3
bogomips : 7127.93
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:==================================
So my virtual machine has lots of extra goodies such as sse2 &sse3, so it could be one those that are illegal on the older chips.
I can't be bothered to try and compile from scratcha dn debug. I'll just continue using the 32 bit virtual machine to play....
Thanks anyway.
-
Glad to hear!
BTW, just out of curiosity: we now know that the welcome plugin was the culprit. But I'm thinking, that plugin couldn't be the only part of QtCreator using SSE2 and 3? Maybe it's the video after all (but not python :-)
If you have the time, test for example a youtube video in the virtual machine, if the VM survives that or not... -
Hi,
The two old machines work fine for all other apps that I can test, including YouTube.
I was using them because they have serial ports and I wanted to develop a serial application. I can't bear the pain of trying to get them to work, so I have purchased a cheap PCI express card for my main machine with 2 x serial and 1 x parallel ports. At £25/30€ it's worth being able to use the infinitely more powerful 64-bit machine.
Also, this one is in my front room and the others are in the attic 8^)
Thanks for the help anyway.
