#211 Program or Verify command crashes piclab

[Darrell]

piclab used to work fine with the PICkit1 programmer on a USB port. Now versions 0.15.3 (Fedora 9) and 0.15.4 (Mandriva 2009.1) crash when trying to PROGRAM or VERIFY. But, the other operations still work OK. The crash is 100% repeatable.

* READ works OK.
* BLANK CHECK works OK.
* ERASE works OK.
* VERIFY crashes. The shell error is:
CRASH_ASSERT: "_value!=Nb_Types" in ../../src/common/common/purl_base.h (36)
KCrash: Application 'piklab' crashing...
KCrash cannot reach kdeinit, launching directly.
* PROGRAM crashes. The same shell error:
CRASH_ASSERT: "_value!=Nb_Types" in ../../src/common/common/purl_base.h (36)
KCrash: Application 'piklab' crashing...
KCrash cannot reach kdeinit, launching directly.

I then launched it using gdb. Selecting the VERIFY command, piklab crashes immediately and gives the following error:
CRASH_ASSERT: "_value!=Nb_Types" in ../../src/common/common/purl_base.h (36)
Program received signal SIGSEGV, Segmentation fault.
0x08227ed5 in ?? ()

The backtrace result is:
(gdb) bt
#0 0x08227ed5 in ?? ()
#1 0x08092ba8 in ?? ()
#2 0x080ef3cd in ?? ()
#3 0x080efd04 in ?? ()
#4 0x08083c13 in ?? ()
#5 0x08083eeb in ?? ()
#6 0x08083f96 in ?? ()
#7 0x08084245 in ?? ()
#8 0x080d0ae3 in ?? ()
#9 0x05cb6b5a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0x05cb866b in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x05718789 in KAction::activated () from /usr/lib/libkdeui.so.4
#12 0x057622b0 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#13 0x05761eb4 in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#14 0x05807c13 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#15 0x05cb6b5a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x057640e3 in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#17 0x057641c0 in KToolBarButton::mouseReleaseEvent () from /usr/lib/libkdeui.so.4
#18 0x05cf3df1 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x057b76c1 in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#20 0x05c4ddbd in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x05c4f13f in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x054f6102 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0x05be56be in QApplication::sendSpontaneousEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x05be514f in QETWidget::translateMouseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x05be436a in QApplication::x11ProcessEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x05bf63bb in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x05c684a0 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x05c68366 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x05c4e49f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x08083287 in QFrame::qt_emit ()
#31 0x0075e5d6 in __libc_start_main () from /lib/libc.so.6
#32 0x080830e1 in QFrame::qt_emit ()

Using usb_pickit_1.5-jeb from command line I have verified that the hardware and programmer are OK. I did see elsewhere to run piklab-prog with the --max-debug option but don't know what parameters to use for the "programmer" and for the"device". It used to work fine previously but I don't know what version it was about a year ago.