Subject:
pikdev crashes
From:
"Maxim Wexler" ####@####.####
Date:
2 Sep 2006 15:56:52 +0100
Message-Id: <a0811460609020756r50311624o574bdda65b51dc77@mail.gmail.com>
Hi group,
I sent this message earlier but it doesn't appear in my browser. Apologies
if you've seen it already.
I've installed pikdev071/kde352 on a gentoo box and it crashes whenever I
try to configure the parport.
Yes, parport, ppdev and parport_pc are loaded.
Here's the backtrace:
Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7485)]
[KCrash handler]
#6 0xb5e309f0 in rawmemchr () from /lib/libc.so.6
#7 0xb5e27715 in _IO_str_init_static_internal () from /lib/libc.so.6
#8 0xb5e1c95d in vsscanf () from /lib/libc.so.6
#9 0xb5e1812b in sscanf () from /lib/libc.so.6
#10 0x0805ce6b in parport::setport (this=0x83bcce8, np=0xb5edaff4
"\034=\021")
at uparport.cc:86
#11 0x0809018a in hardware::setpins (this=0x823ce74, port_type=0x0,
portname=0x0, vpp=0, vdd=0, clk=0, datao=2, datai=0, rw=0)
at hardware.cc:39
#12 0x0806d08e in PrgConfig::doApply (this=0x8394da8) at PrgConfig.cpp:360
#13 0x0806d2f2 in PrgConfig::doOk (this=0x8394da8) at PrgConfig.cpp:380
#14 0x080a1bfc in PrgConfig::qt_invoke (this=0x8394da8, _id=62,
_o=0xbfd75610)
at PrgConfig.moc.cc:136
#15 0xb651567c in QObject::activate_signal (this=0x84224b0, clist=0x8422d60,
o=0xbfd75610) at qobject.cpp:2355
#16 0xb65154d4 in QObject::activate_signal (this=0x84224b0, signal=4)
at qobject.cpp:2324
#17 0xb6901987 in QButton::clicked (this=0x84224b0) at moc_qbutton.cpp:152
#18 0xb65c3f96 in QButton::mouseReleaseEvent (this=0x84224b0, e=0xbfd75aa0)
at qbutton.cpp:836
#19 0xb6558b05 in QWidget::event (this=0x84224b0, e=0xbfd75aa0)
at qwidget.cpp:4676
#20 0xb64a5205 in QApplication::internalNotify (this=0xbfd75fc0,
receiver=0x84224b0, e=0xbfd75aa0) at qapplication.cpp:2635
#21 0xb64a4738 in QApplication::notify (this=0xbfd75fc0, receiver=0x84224b0,
e=0xbfd75aa0) at qapplication.cpp:2421
#22 0xb6e2c035 in KApplication::notify (this=0xbfd75fc0, receiver=0x84224b0,
event=0xbfd75aa0) at kapplication.cpp:550
#23 0xb642cd0e in QApplication::sendSpontaneousEvent (receiver=0x84224b0,
event=0xbfd75aa0) at qapplication.h:494
#24 0xb6424a50 in QETWidget::translateMouseEvent (this=0x84224b0,
event=0xbfd75e60) at qapplication_x11.cpp:4291
#25 0xb6422318 in QApplication::x11ProcessEvent (this=0xbfd75fc0,
event=0xbfd75e60) at qapplication_x11.cpp:3442
#26 0xb6440295 in QEventLoop::processEvents (this=0x818b0a8, flags=4)
at qeventloop_x11.cpp:192
#27 0xb64bc7a9 in QEventLoop::enterLoop (this=0x818b0a8) at qeventloop.cpp
:198
#28 0xb64bc6c2 in QEventLoop::exec (this=0x818b0a8) at qeventloop.cpp:145
#29 0xb64a53a7 in QApplication::exec (this=0xbfd75fc0) at qapplication.cpp
:2758
#30 0x0807fd22 in main (argc=0, argv=0x0) at pikdev.cpp:87
I searched bugs.kde.org but came up empty. Can someone interpret this?
-Maxim
