[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: arora qt4 and segmentation fault on nslu2



Am Donnerstag 07 August 2008 09:31:11 schrieb Riku Voipio:

> have you tried the arm eabi port (armel?). I couldn't
> reproduce the problem there.
no, it seems for me that there is no proper way to
Migrating arm installation to arm EABI installation

> please install libqt4-dbg for a better backtrace and
this is the output with libqt4-dbg

/usr/lib/qt4/examples/dialogs/standarddialogs$ gdb ./standarddialogs
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting 
program: /usr/lib/qt4/examples/dialogs/standarddialogs/standarddialogs
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x413c8ab0 (LWP 17424)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x413c8ab0 (LWP 17424)]
0x401d2000 in QKeyMapper::changeKeyboard () at kernel/qkeymapper.cpp:93
93      kernel/qkeymapper.cpp: No such file or directory.
        in kernel/qkeymapper.cpp
Current language:  auto; currently c++
(gdb) backtrace
#0  0x401d2000 in QKeyMapper::changeKeyboard () at kernel/qkeymapper.cpp:93
#1  0x401e9f48 in qt_init (priv=0x1e718, display=0x0, visual=0, colormap=0)
    at kernel/qapplication_x11.cpp:1902
#2  0x40157f38 in QApplicationPrivate::construct (this=0x1e718, dpy=0x0, 
visual=0, cmap=0)
    at kernel/qapplication.cpp:740
#3  0x401597b8 in QApplication (this=0xbebea888, argc=@0xbebea828, 
argv=0xbebea944, _internal=263168)
    at kernel/qapplication.cpp:672
#4  0x0001363c in ?? ()
(gdb)                    

> file against libqtgui4
ok i will try


with all qt4 examples and demos i have tested
i get the same result


Reply to: