25 May
2008
25 May
'08
7:35 a.m.
On Sat, May 24, 2008 at 11:01:07PM +0100, Rui Nuno Capela wrote:
James Stone wrote:
Oh yes.. silly me!
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6e86940 (LWP 5355)]
0xb72c493c in memcpy () from /lib/i686/cmov/libc.so.6
(gdb) bt
#0 0xb72c493c in memcpy () from /lib/i686/cmov/libc.so.6
#1 0xb753101c in QString::QString () from /usr/lib/libQtCore.so.4
#2 0xb75313b0 in QString::mid () from /usr/lib/libQtCore.so.4
#3 0xb755d578 in QAbstractFileEngine::create () from /usr/lib/libQtCore.so.4
#4 0xb7572777 in ?? () from /usr/lib/libQtCore.so.4
#5 0xb75ddf01 in QCoreApplication::applicationDirPath ()
from /usr/lib/libQtCore.so.4
#6 0xb74e8d2b in ?? () from /usr/lib/libQtCore.so.4
#7 0xb74e8ef7 in ?? () from /usr/lib/libQtCore.so.4
#8 0xb74e8f66 in ?? () from /usr/lib/libQtCore.so.4
#9 0xb74e908b in QLibraryInfo::location () from /usr/lib/libQtCore.so.4
#10 0xb75dea3d in QCoreApplication::libraryPaths ()
from /usr/lib/libQtCore.so.4
#11 0xb75df17b in QCoreApplication::init () from /usr/lib/libQtCore.so.4
#12 0xb75df3d7 in QCoreApplication::QCoreApplication ()
from /usr/lib/libQtCore.so.4
#13 0xb77ec285 in QApplication::QApplication () from /usr/lib/libQtGui.so.4
#14 0x08057867 in main (argc=Cannot access memory at address 0x3e69fda
) at src/main.cpp:33
James
For some reason qjackctl has started to segfault
on startup. I
have not got a clue what is happening. It was working fine fairly
recently.
Here is all I get from gdb:
Starting program: /usr/local/bin/qjackctl
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f0c940 (LWP 9865)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6f0c940 (LWP 9865)]
0xb734a93c in memcpy () from /lib/i686/cmov/libc.so.6
(gdb) quit
I am on Debian sid.
Any ideas??
yes, try entering "bt" for a backtrace instead of "quit" in the gdb
prompt
:)