@vedranMv said in Seg fault when deleting Q3DScatter object:

Regarding your edit, what you're writing makes perfect sense, but as you can see in the code, it's the other way around. If I don't call delete manually, I get a segfault.

Then it seems to me there must be something else wrong in your code.

@takti You need to understand that most people in this forum are volunteers spending their own time to help others for free. This includes me as well. Since I don't have a solution for your problem I suggested to check somewhere else also.

@mrjj Thank you for your tip. Its great help for a QT and C++ beginner. I'll try to implement the logic you mentioned.

@sierdzio said in Segfault core dumped:

Anyway, the bug is in line 61 in = &inFile; - you assign a variable created on a stack to variable in. In the next line, the inFile goes out of scope and is deleted. So when you try to access in later in the code, it segfaults.

Thanks !! . I know it's not Qt problem but that's why i posted it in C++ section

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!