** Changed in: qt4-x11 (Ubuntu Natty)
Milestone: natty-alpha-2 = natty-alpha-3
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/705689
Title:
unity-2d-launcher crashes with segfault
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
When disassembling the 10.10 Qt library which has ittt no warning is
given, so that was probably a false trail, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705689
Title:
unity-2d-launcher
Yeah, I'm agreeing with Jani, that was a false trail. here's the new
backtrace with ittt in the patch and unity-2d rebuilt against it:
(gdb) bt
#0 0x404fce2c in operator int (this=0xdf6ce0,
parent=value optimized out)
at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:85
So after active debugging on #linaro, I tore apart some maverick
binaries built against stock-maverick qt4-x11, which has implicate-its
enabled, and found the compiler generated an 'i' instruciton vs
'ittt'.
I'm currently testbuilding a new version of Qt with this modification.
--
You
Test code on maverick (no explicate it block):
mcasadevall@risingsun:/srv/chroots/maverick-armel$ cat test.c
#include stdio.h
int _q_value = 10;
inline bool testAndSetOrdered(int expectedValue, int newValue)
{
register int result;
asm volatile(0:\n
ldrex %[result],
An alternatve to rebuilding Qt with the patch applied is to binary patch
the Qt libs and test:
I copied libQtCore.so and libQtGui.so (the two Qt deps of the simple Qt app
which crashes) in the current dir
Then
sed -i 's/\x04\(\xbf.\xe8\x00.\)/\x02\1/' libQtCore.so.4
same on QtGui
export
Hi Jani,
Assuming for the moment that sed didn't trip over any other matching chunk of
binary, ok, but
It's not clear to me why the assembler is warning on that branch; can you
disassemble the 4 or 5 instructions leading up to that?
My reading of binutils is that it prints that message
Definitely not a unity-2d bug :)
This simple app build on pandaboard and current natty crashes in the same way
as the launcher (in QReadUnlock())
Crashes 4 runs out of 5 maybe, built with either g++-4.4 or g++4.5
//to build: c++ -I/usr/include/qt4 -I/usr/include/qt4/QtGui
crashercpp -lQtGui
Did another round of tests, with maverick build 4.7.0 with the natty IT
patch added (posted above) and I got a segfault similar to the one we
got earlier, which leads me to believe we have a bad patch.
Backtrace is identical to current faults. Looks like this is a bad
patch to Qt vs. a gcc
** Also affects: gcc-4.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705689
Title:
unity-2d-launcher crashes with segfault error on armel
Opening new task on gcc-4.5 due to possibility of compiler regression.
Attempting to build natty's Qt on maverick caused a compiler ICE, but
since I was building in sbuild, I lost the build environment when it
failed. Will try and rerun build at some point so I can file that bug. I
was pointed at
On a hunch that we're looking at a possible compiler regression, I
recompiled the maverick Qt 4.7.0 source package against natty (and added
the thumb2 patch attached below from the 4.7.1 package) and installed it
on a working natty system which still developed a segfault.
Backtrace with 4.7.0
** Also affects: qt4-x11 (Ubuntu Natty)
Importance: High
Assignee: Michael Casadevall (mcasadevall)
Status: Confirmed
** Changed in: unity-2d
Status: New = Invalid
** Changed in: qt4-x11 (Ubuntu Natty)
Milestone: None = natty-alpha-2
** Changed in: unity-2d
14 matches
Mail list logo
