Package: vite
Version: 1.2-3
Severity: important

When starting vite with no argument, it segfaults immediately. 
I get the following backtrace:


Reading symbols from /usr/bin/vite...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/vite 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe50cd700 (LWP 17359)]

Program received signal SIGSEGV, Segmentation fault.
0x0000003507abd9a0 in QString::fromLocal8Bit(char const*, int) () from 
/usr/lib/libQtCore.so.4
(gdb) bt
#0  0x0000003507abd9a0 in QString::fromLocal8Bit(char const*, int) () from 
/usr/lib/libQtCore.so.4
#1  0x0000003507b62e7b in QCoreApplication::arguments() () from 
/usr/lib/libQtCore.so.4
#2  0x000000350ac4e281 in ?? () from /usr/lib/libQtGui.so.4
#3  0x000000350ac4ee39 in ?? () from /usr/lib/libQtGui.so.4
#4  0x0000003504204ef7 in _SmcProcessMessage () from 
/usr/lib/x86_64-linux-gnu/libSM.so.6
#5  0x0000003504611846 in IceProcessMessages () from 
/usr/lib/x86_64-linux-gnu/libICE.so.6
#6  0x000000350ac3d47f in ?? () from /usr/lib/libQtGui.so.4
#7  0x0000003507b73eba in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) () from /usr/lib/libQtCore.so.4
#8  0x0000003507bbd42e in QSocketNotifier::activated(int) () from 
/usr/lib/libQtCore.so.4
#9  0x0000003507b7bb6b in QSocketNotifier::event(QEvent*) () from 
/usr/lib/libQtCore.so.4
#10 0x000000350abcfc64 in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/libQtGui.so.4
#11 0x000000350abd4af1 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libQtGui.so.4
#12 0x0000003507b6128c in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/libQtCore.so.4
#13 0x0000003507b8b557 in ?? () from /usr/lib/libQtCore.so.4
#14 0x00007ffff637d0cf in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff637d8c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff637da99 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x0000003507b8be2f in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#18 0x000000350ac73eee in ?? () from /usr/lib/libQtGui.so.4
#19 0x0000003507b60492 in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#20 0x0000003507b6068f in 
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#21 0x0000003507b64837 in QCoreApplication::exec() () from 
/usr/lib/libQtCore.so.4
#22 0x00000000004b152c in ?? ()
#23 0x00007ffff6c9eead in __libc_start_main (main=<optimized out>, 
argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, 
fini=<optimized out>, rtld_fini=<optimized out>, 
    stack_end=0x7fffffffe208) at libc-start.c:228
#24 0x00000000004226b9 in ?? ()
#25 0x00007fffffffe208 in ?? ()


If a trace file is given as argument, it starts, but crashes upon some 
operations, such as: enter manually a zoom value in textbox, open menu
File > Settings, display tooltips when mouse cursor hoovers toolbar icons.


When building from sources downloaded from INRIA gforge, it works ok.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (950, 'unstable'), (940, 'experimental'), (500, 'testing'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.iso885915@euro, LC_CTYPE=fr_FR.iso885915@euro 
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages vite depends on:
ii  libc6                     2.13-27
ii  libgcc1                   1:4.6.3-1
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libglu1-mesa [libglu1]    7.11.2-1
ii  libqt4-opengl             4:4.7.4-2
ii  libqt4-xml                4:4.7.4-2
ii  libqtcore4                4:4.7.4-2
ii  libqtgui4                 4:4.7.4-2
ii  libstdc++6                4.6.3-1
ii  zlib1g                    1:1.2.6.dfsg-2

vite recommends no packages.

vite suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to