@JonnyQB
Hi
You declare it like
Punkte * punkten;

Then some place else you must do
punkten = new Punkte(); ( not in .h)
Often the constructor is a good place.

Hi @Tegan,

Not sure what the best approach is, but I'd:

check the installer's md5sum against https://download.qt.io/archive/qt/5.6/5.6.3/md5sums.txt compare the output of ldd qt-opensource-linux-x64-5.6.3.run on both hosts, then run the installer with gdb

Cheers.

Yeah. It happens when you copy&paste without double check comments and you're afraid about "it could not work" :)
Thanks!

@tomasz3dk Wielkie dzięki, pomogło :)

@AlterX Ok, I see, I will change this for the device internal pointers, but the "currentDevice" is used many times from outside to access that data. That's why I kept it public, I didn't really see much sense it making that private and then allow to read it anyway. I see the issue of it being written from outside, but I checked all occurences and they all solely query data and call methods, so I didn't think it helps me with the segmentation fault, what do you think?

Stephan

Hi, i was experiencing the same strange thing... i was using Qt headers and non Qt headers, and placing before the Qt headers seemed to have solved the problem.

@JKSH It is latest version of MinGW. But everything works fine with Qt version of MinGW. Thank you so much for help!