[Qt-interest] Qt 4.7.0 application Segmentation Fault on Mx51
Manoj Agrawal
Manoj.Agrawal at maxim-ic.com
Fri Jan 21 10:38:30 CET 2011
I tried building with default optimization i.e. O2 but no help!! Now I am trying to build Qt 4.6.3 if that helps.
R/Manoj
-----Original Message-----
From: qt-interest-bounces+manoj.agrawal=maxim-ic.com at qt.nokia.com [mailto:qt-interest-bounces+manoj.agrawal=maxim-ic.com at qt.nokia.com] On Behalf Of Manoj Agrawal
Sent: Friday, January 21, 2011 2:05 PM
To: Donald Carr
Cc: qt-interest at qt.nokia.com
Subject: Re: [Qt-interest] Qt 4.7.0 application Segmentation Fault on Mx51
I downloaded qt-everywhere-opensource-src-4.7.0.tar.gz from downloads section on qt.nokia.com, can that make a difference?
I can not get rid of -fno-rtti flag as some of other libraries are using this flag and my application does not build in that case. I used -O3 for performance reasons, I can try building without the same.
R/Manoj
-----Original Message-----
From: Donald Carr [mailto:sirspudd at gmail.com]
Sent: Friday, January 21, 2011 1:47 PM
To: Manoj Agrawal
Cc: qt-interest at qt.nokia.com
Subject: Re: [Qt-interest] Qt 4.7.0 application Segmentation Fault on Mx51
Hey,
Firstly, could you abstain from using those patches, in order for us
to establish that they are not involved.
qmake.conf.patch is a harmless if odd inclusion
g++.conf.patch sets needlessly aggressive -O flags (which could air
some skeletons in the toolchain you are using) and disables rtti, the
full implications of which are lost on me. Neither are required and it
would be useful to establish whether this manifests without these
patches.
I think I used the code sourcery g++ lite 2009q1 with that device, and
had to deploy the compilers libstdc++.so to the target since the
system libstdc++ was a little long in the tooth. My point is I am not
familiar with the toolchain shipped as part of their BSP.
I have to stress that something is amiss here, I stick Qt on every
flavor of Arm device that crosses my desk, and I have never seen this
particular crash.
We need to establish whether a virgin Qt build reproduces this behavior.
I have to stress that you would be better off with a fresh checkout of Qt 4.7:
http://qt.gitorious.org/qt
rather than the 4.7.0 package. Did you grab the package from our ftp site?
Yours sincerely,
Donald
On Thu, Jan 20, 2011 at 11:12 PM, Manoj Agrawal
<Manoj.Agrawal at maxim-ic.com> wrote:
> Hi Donald,
>
> I am building Qt in debug_and_release mode using Linux_2.6.31_SDK1.7 version from mx51 bsp.
> I did not get what do you mean by "building it from scratch?" I am extracting sources and then only building it.
> Please find attached g++.conf.patch and qmake.conf.patch, I am applying to this build.
>
> Thanks and Regards,
> Manoj
>
> -----Original Message-----
> From: Donald Carr [mailto:sirspudd at gmail.com]
> Sent: Friday, January 21, 2011 12:28 PM
> To: Manoj Agrawal
> Cc: qt-interest at qt.nokia.com
> Subject: Re: [Qt-interest] Qt 4.7.0 application Segmentation Fault on Mx51
>
> Hey Manoj,
>
> What toolchain are using to compile Qt for the i.MX51?
>
> I have deployed Qt 4.7 to that hardware without any hitches, my
> primary suspicion is your toolchain.
> What base system you using? (I think the standard Freescale BSP env is ALIP?)
>
> Are you building it from scratch?
>
> Worst case scenario you can enable a debug build of Qt and get a
> better stack trace.
>
> Please attach the qmake.conf from your mkspec
>
> Yours sincerely,
> Donald
>
> On Thu, Jan 20, 2011 at 10:51 PM, Manoj Agrawal
> <Manoj.Agrawal at maxim-ic.com> wrote:
>> Hello,
>>
>>
>>
>> I recently upgraded to Qt 4.7.0 from Qt 4.5.3 due to a specific keyboard
>> event issue (I don't get Qt::Key_Enter release) on Mx51. Keyboard event
>> issue got resolved but I got into segmentation fault in libqjpeg.so. My
>> application runs and works fine but crashes at some points with following
>> core dump:
>>
>>
>>
>> Program terminated with signal 11, Segmentation fault.
>>
>> #0 0x2ef87958 in ?? ()
>>
>> from /root/release_mx51_project/plugins/imageformats/libqjpeg.so
>>
>>
>>
>> I did some google and found that people have faced similar segmentation
>> faults and resolved using -no-freetype in configuration options. But looks
>> like, my problem is different as it is crashing in jpeg plug-in.
>>
>>
>>
>> I am using following configuration options
>>
>> CONFIG_OPTS=-v -confirm-license \
>>
>> -opensource \
>>
>> -debug-and-release \
>>
>> -embedded arm \
>>
>> -platform /qws/linux-x86-g++ \
>>
>> -xplatform /qws/linux-arm-gnueabi-g++ \
>>
>> -little-endian \
>>
>> -openssl \
>>
>> -qt-gfx-linuxfb \
>>
>> -qt-zlib \
>>
>> -qt-libjpeg \
>>
>> -qt-gif \
>>
>> -qt-libtiff \
>>
>> -qt-libpng \
>>
>> -qt-libmng \
>>
>> -fast \
>>
>> -no-dbus \
>>
>> -no-javascript-jit \
>>
>> -no-largefile \
>>
>> -qt-sql-sqlite \
>>
>> -no-qt3support \
>>
>> -no-webkit \
>>
>> -no-cups \
>>
>> -no-mmx \
>>
>> -no-3dnow \
>>
>> -no-sse \
>>
>> -no-sse2 \
>>
>> -no-svg \
>>
>> -no-scripttools \
>>
>> -nomake examples \
>>
>> -nomake demos \
>>
>> -nomake docs \
>>
>>
>> -L$(PROJECT_ROOT)/dist/opt/freescale/bsp/mx51/L2.6.31_10.05.02_ER_source/rootfs/usr/lib
>> \
>>
>>
>> -I$(PROJECT_ROOT)/dist/opt/freescale/bsp/mx51/Linux_2.6.31_SDK1.7/rootfs/usr/include
>> \
>>
>>
>> -I$(PROJECT_ROOT)/dist/opt/freescale/bsp/mx51/Linux_2.6.31_SDK1.7/rootfs/usr/include/openssl
>>
>>
>>
>> Any pointers on this will be great help. Please let me know if I should also
>> supply g++ and qmake patches, I am applying for this build.
>>
>>
>>
>> Thanks and Regards,
>>
>> Manoj
>>
>> _______________________________________________
>> Qt-interest mailing list
>> Qt-interest at qt.nokia.com
>> http://lists.qt.nokia.com/mailman/listinfo/qt-interest
>>
>>
>
>
>
> --
> -------------------------------
> °v° Donald Carr
> /(_)\ Professional Penguin lover
> ^ ^
>
--
-------------------------------
°v° Donald Carr
/(_)\ Professional Penguin lover
^ ^
_______________________________________________
Qt-interest mailing list
Qt-interest at qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-interest
More information about the Qt-interest-old
mailing list