SIGSEGV when using T2CON

Bug #119595 reported by dzs
6
Affects Status Importance Assigned to Milestone
ktechlab (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ktechlab

When I run the following program in ktechlab, I got a SIGSEGV. Usually not for the first time but for the 2nd or 3rd.

Program:

 processor p16f628
 include <p16f628.inc>

 banksel T2CON
 movlw 0x04
 movwf T2CON

loop
 nop
 goto loop

 end

Call stack:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[repeats several times]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1244174640 (LWP 3849)]
(no debugging symbols found)
[repeats several times]
(no debugging symbols found)
[KCrash handler]
#6 0xb7ddcdb5 in TMR2::callback () from /usr/lib/libgpsim.so.0
#7 0xb7e0fc6b in Cycle_Counter::breakpoint () from /usr/lib/libgpsim.so.0
#8 0xb7e4d9eb in Program_Counter::jump () from /usr/lib/libgpsim.so.0
#9 0xb7e4e48d in GOTO::execute () from /usr/lib/libgpsim.so.0
#10 0xb7dd60f0 in pic_processor::step_one () from /usr/lib/libgpsim.so.0
#11 0x0821a267 in ?? ()
#12 0x08148a6b in ?? ()
#13 0x08148c7a in ?? ()
#14 0xb662788b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb6628330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb69b5ba6 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#17 0xb664f596 in QTimer::event () from /usr/lib/libqt-mt.so.3
#18 0xb65bea60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0xb65c088f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0xb6d83ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0xb65511e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#22 0xb65b14ab in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#23 0xb6565d25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#24 0xb65d9136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#25 0xb65d8f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#26 0xb65c0609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#27 0x082da4e3 in ?? ()
#28 0xb5dfbebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#29 0x0807caa1 in ?? ()

Revision history for this message
Jeff Anderson (jander99) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in ktechlab (Ubuntu):
status: New → Incomplete
Revision history for this message
dzs (dzsabor) wrote :

I don't work with ktechlab recently, but I made a quick test and it worked.

As ktechlab seems to be dead (the newest release was before I submitted this bug) I'm not sure whether this was a packaging problem and fixed since or I just got lucky while testing.

Revision history for this message
xteejx (xteejx) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in ktechlab (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.