The unity-2d-launcher crash can be reproduced with a locally built Qt, however the app I pasted in comment #9 works.
I built Qt with regular system libs and not in a chroot so maybe there's a slight difference.
As seen for the sample app, if I built Qt with either g++ or gcc 4.4(there are both C++ and C files in the source) the crash is similar, so I don't think this is a compiler regression.
The bug occurs when accessing a volatile int member of a struct via an int() operator defined on that class and which simply returns the value.
The unity-2d-launcher crash can be reproduced with a locally built Qt, however the app I pasted in comment #9 works.
I built Qt with regular system libs and not in a chroot so maybe there's a slight difference.
As seen for the sample app, if I built Qt with either g++ or gcc 4.4(there are both C++ and C files in the source) the crash is similar, so I don't think this is a compiler regression.
The bug occurs when accessing a volatile int member of a struct via an int() operator defined on that class and which simply returns the value.
QBasicAtomicInt class in this file qt.gitorious. org/qt/ qt/blobs/ 4.7/src/ corelib/ thread/ qbasicatomic. h
http://
The two crashes I have seen both access that field from within the macro Q_DECLARE_METATYPE at line 265 in qt.gitorious. org/qt/ qt/blobs/ 4.7/src/ corelib/ kernel/ qmetatype. h
http://
That macro is used to define GestureState metatype, the one seen in the stacktraces above.
I'll try to check whether https:/ /bugs.launchpad .net/gcc- linaro/ +bug/675347 is related.