segmentation fault

[Milav]

@jsulm said in segmentation fault:

OK, maybe we should start from the beginning.

Okay sure.

@jsulm said in segmentation fault:

Do you cross compile from PC to device?

Yes i cross compile the "qt-mosquitto" application for target (device) from qt creator (that is install on pc).

For cross compilng i have use qmake version 4.8.7.

and qt creator version is "Qt Creator 3.3.0 (opensource)"

and for v

@jsulm said in segmentation fault:

Does the app crash in same way on host with Qt5?

No, the application is not crash in PC.

In pc i have use same code but qmake vwersion is 5.4.0

@jsulm said in segmentation fault:

Is it possible that you're mixing Qt4 and Qt5 on your target device? You can check this using "ldd EXECUTABLE" on your target.

In target i have only qt 4 library and qmake are there.
i think there is no qt 5 component in target device.

@jsulm said in segmentation fault:

Please do this on your target (in a terminal):

sorry for this, but i have not ldd command on target device.
if it is necessary than tell i have install and cross compile it for target device.

sorry i dont know why this ldd cmd is not there in target device.

[jsulm]

@Milav said in segmentation fault:

sorry i dont know why this ldd cmd is not there in target device

This is not unusual. On limited devices manufacturers usually remove everything not needed when using the device.
Is "file" command there?

[Milav]

@jsulm said in segmentation fault:

This is not unusual. On limited devices manufacturers usually remove everything not needed when using the device.
Is "file" command there?

Okay no problem.

actually "file" cmd also not in target device.

but in desktop pc i have "file" cmd so i execute file cmd with binary application file.

here i have show output of that .

tdp0009@tdp0009-desktop:~$ file qt-mosquitto 
qt-mosquitto: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-, for GNU/Linux 2.6.32, not stripped

i think you got your answer from above result.

[jsulm]

@Milav said in segmentation fault:

32-bit LSB executable, ARM, EABI5

Looks good if that's what your target device CPU is

[Milav]

@jsulm said in segmentation fault:

Looks good if that's what your target device CPU is

yes. it is ARM based 32-bit CPU.

[Milav]

@jsulm said in segmentation fault:

ldd /opt/milav/qt-mosquitto

hello ,

i explore and find some of the cmd for ldd.

here i have show the output for ldd qt-mosquitto/

  Shared library: [libmosquittopp.so.1]
 0x00000001 (NEEDED)                     Shared library: [libmosquitto.so.1]
 0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
 0x00000001 (NEEDED)                     Shared library: [librt.so.1]
 0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
 0x00000001 (NEEDED)                     Shared library: [libstdc++.so.6]
 0x00000001 (NEEDED)                     Shared library: [libm.so.6]
 0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x00000001 (NEEDED)                     Shared library: [ld-linux-armhf.so.3]

hope now you got your answer.

[Milav]

@jsulm

Hello, have you got any solution?

[jsulm]

@Milav Did you try to cross compile a simple application and run it on your device?

[Milav]

@jsulm

yes, without mqtt module , i tried lot of application and it is working very fine..

[jsulm]

@Milav Then I suggest to start with a minimal application and add mqtt functionality in small pieces to see when it starts to crash.

[Pablo J. Rogina]

@Milav said in segmentation fault:

the difference between host pc and Embedded target board is only QT source.
Host pc => qmake (qt version 5.4.0 )
Embedded target => qmake (qt version 4.8.7)

You should have stated these settings from the very beginning... :-)

Anyway, could it be possible that you build Qt 4.8.7 for PC (host) and build your example again with that Qt version and run in PC to see what happens.