I have been able to eliminate the segfaults by turning off compiler
optimization by changing -O2 to -O0 in mkspecs/common/g++.conf.
I can live with this but I would still like to know what's wrong.
--- In "jasonpenn_1981" <> wrote:
>
> Many of the Qt "demo" applications fail to function. They die with
> segmentation faults on startup. Gdb doesn't display a useful stack trace -
> just zeros.
>
> My build environment is a 'dd' image of the SD card root filesystem mounted
> via loopback on a Ubuntu box. The Ubuntu box has qemu-user-static installed
> on it. I run Qt's configure/make in a chroot() of the SD card root filesystem.
>
> A few months ago I built Qt Embedded 4.7.3 for the TS-TPC-7390 running
> Lenny/EABI and have been using it almost daily developing an HMI application.
> It works fine as do the Qt demos.
>
> Without useful gdb crash information I have no idea what's wrong. Playing
> "divide and conquer" with my HMI application it seems like the crash is in Qt
> somewhere related to fonts. If I comment out the calls to set larger font
> sizes my HMI application doesn't crash.
>
> If I can't get Qt running on the 8390 very soon I will have to bail on it for
> a product design and revert to the 7390. Any help is most appreciated.
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|