gnupic: pikdev signal 11
Subject:
pikdev signal 11
From:
"Maxim Wexler" ####@####.####
Date:
2 Sep 2006 02:47:54 +0100
Message-Id: <a0811460609011847i35001e25m281347c0fbf6af03@mail.gmail.com>
Hi group,
When I start pikdev it asks me to configure the parallel port so I click
->Configure ->Programmer and just accept the defaults by clicking 'apply'.
Then pikdev crashes. Here's the output from KDE Crash Handler:
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 13861)]
[KCrash handler]
#6 0xb5eac9f0 in rawmemchr () from /lib/libc.so.6
#7 0xb5ea3715 in _IO_str_init_static_internal () from /lib/libc.so.6
#8 0xb5e9895d in vsscanf () from /lib/libc.so.6
#9 0xb5e9412b in sscanf () from /lib/libc.so.6
#10 0x0805ce6b in parport::setport (this=0x83c2798, np=0xb5f56ff4
"\034=\021")
at uparport.cc:86
#11 0x0809018a in hardware::setpins (this=0x823ce94, 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=0x83a1640) at PrgConfig.cpp:360
#13 0x080a1c0e in PrgConfig::qt_invoke (this=0x83a1640, _id=61,
_o=0xbfaf0e90)
at PrgConfig.moc.cc:135
#14 0xb659167c in QObject::activate_signal (this=0x83c0b00, clist=0x83c10e0,
o=0xbfaf0e90) at qobject.cpp:2355
#15 0xb65914d4 in QObject::activate_signal (this=0x83c0b00, signal=4)
at qobject.cpp:2324
#16 0xb697d987 in QButton::clicked (this=0x83c0b00) at moc_qbutton.cpp:152
#17 0xb663ff96 in QButton::mouseReleaseEvent (this=0x83c0b00, e=0xbfaf1320)
at qbutton.cpp:836
#18 0xb65d4b05 in QWidget::event (this=0x83c0b00, e=0xbfaf1320)
at qwidget.cpp:4676
#19 0xb6521205 in QApplication::internalNotify (this=0xbfaf1840,
receiver=0x83c0b00, e=0xbfaf1320) at qapplication.cpp:2635
#20 0xb6520738 in QApplication::notify (this=0xbfaf1840, receiver=0x83c0b00,
e=0xbfaf1320) at qapplication.cpp:2421
#21 0xb6ea8035 in KApplication::notify (this=0xbfaf1840, receiver=0x83c0b00,
event=0xbfaf1320) at kapplication.cpp:550
#22 0xb64a8d0e in QApplication::sendSpontaneousEvent (receiver=0x83c0b00,
event=0xbfaf1320) at qapplication.h:494
#23 0xb64a0a50 in QETWidget::translateMouseEvent (this=0x83c0b00,
event=0xbfaf16e0) at qapplication_x11.cpp:4291
#24 0xb649e318 in QApplication::x11ProcessEvent (this=0xbfaf1840,
event=0xbfaf16e0) at qapplication_x11.cpp:3442
#25 0xb64bc295 in QEventLoop::processEvents (this=0x818b0a8, flags=4)
at qeventloop_x11.cpp:192
#26 0xb65387a9 in QEventLoop::enterLoop (this=0x818b0a8) at qeventloop.cpp
:198
#27 0xb65386c2 in QEventLoop::exec (this=0x818b0a8) at qeventloop.cpp:145
#28 0xb65213a7 in QApplication::exec (this=0xbfaf1840) at qapplication.cpp
:2758
#29 0x0807fd22 in main (argc=0, argv=0x0) at pikdev.cpp:87
I did a search at bugs.kde.org but came up empty. Can someone here make
sense of this?
-Maxim