#33 Crashed valknut on start
Linux version 2.6.24-1-amd64 (Debian 2.6.24-6) (waldi@debian.org) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Fri Apr 18 23:08:22 UTC 2008
Valknut: 0.3.13
DCLIB: 0.3.13
QT compiled: 3.3.8b
QT used: 3.3.8b
LIBXML compiled: 20631
LIBXML used: 20632
[Thread debugging using libthread_db enabled]
[New Thread 0x2ba877084e90 (LWP 14566)]
[New Thread 0x41802950 (LWP 14683)]
[New Thread 0x41001950 (LWP 14570)]
[New Thread 0x40800950 (LWP 14569)]
0x00002ba8766ca282 in select () from /lib/libc.so.6
#0 0x00002ba8766ca282 in select () from /lib/libc.so.6
No symbol table info available.
#1 0x00002ba872db7767 in QEventLoop::processEvents ()
from /usr/lib/libqt-mt.so.3
No symbol table info available.
#2 0x00002ba872e16001 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
No symbol table info available.
#3 0x00002ba872e15eb2 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
No symbol table info available.
#4 0x000000000048953c in main ()
No locals.
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]
Logged In: YES
user_id=1639740
Originator: NO
Can you please recompile dclib and valknut with --enable-debug passed to configure so that the backtrace includes where in main.cpp the crash is. It appears to be before QApplication::exec() has been called, but there are lots of calls to QApplication::processEvents().
Also: there are many problems (mostly fixed in svn) with the build system and header file locations etc. that may cause you to end up with a broken dclib/valknut if you have any older versions of dclib installed when you compile dclib or valknut.