#3 Crash in Pwmleds example

I got crash when I play with Pwmleds. Normaly it works fain, but when i do more (about 6-8) cycles of the Play - Reload - Play - Reload - etc. The cycles are maked while program starts (LED bar lights, do not blinks yet).

The KTL crashes with folowing crash report:

Application: KTechLab (ktechlab), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f2f6e4d502b in Cycle_Counter::reassign_break(unsigned long, unsigned long, TriggerObject*) () from /usr/lib/libgpsim.so.0
#6 0x00007f2f6e52c702 in TMR0::start(int, int) () from /usr/lib/libgpsim.so.0
#7 0x00007f2f6e508ea5 in ADDWF::execute() () from /usr/lib/libgpsim.so.0
#8 0x00007f2f6e5133cf in Processor::step(unsigned int, bool) () from /usr/lib/libgpsim.so.0
#9 0x00007f2f6e506cae in pic_processor::step(unsigned int, bool) () from /usr/lib/libgpsim.so.0
#10 0x00000000005f041b in ?? ()
#11 0x0000000000515604 in ?? ()
#12 0x0000000000515860 in ?? ()
#13 0x00007f2f67229617 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3
#14 0x00007f2f6722b85a in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3
#15 0x00007f2f67249755 in QTimer::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#16 0x00007f2f671cc725 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3
#17 0x00007f2f671cd4aa in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3
#18 0x00007f2f683d550d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4
#19 0x00007f2f671c3023 in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3
#20 0x00007f2f6717dabe in QEventLoop::processEvents(unsigned int) () from /usr/lib/libqt-mt.so.3
#21 0x00007f2f671e2fa1 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#22 0x00007f2f671e2e62 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#23 0x0000000000534c9e in ?? ()
#24 0x00007f2f63a75a8d in __libc_start_main () from /lib/libc.so.6
#25 0x0000000000444739 in ?? ()
#26 0x00007fff8e681138 in ?? ()
#27 0x000000000000001c in ?? ()
#28 0x0000000000000005 in ?? ()
#29 0x00007fff8e682b17 in ?? ()
#30 0x00007fff8e682b20 in ?? ()
#31 0x00007fff8e682b26 in ?? ()
#32 0x00007fff8e682b2f in ?? ()
#33 0x00007fff8e682b38 in ?? ()
#34 0x0000000000000000 in ?? ()

If ktechlab is started from terminal emulator, then lot of messages is writing:

...
attempt write to invalid file register
address 0x1a2, value 0x0
attempt read from invalid file register
address 0x1ab
attempt write to invalid file register
address 0x1ab, value 0x1
attempt read from invalid file register
address 0x1b3
attempt write to invalid file register
address 0x1b3, value 0x1
attempt write to invalid file register
address 0x1b3, value 0x0
FIXME: HLL files are not supported at the moment
TMR2 BUG!! value = d2 which is greater than 0xff
The WDT is not enabled - clrwdt has no effect!

These mesages fill out my console buffer limit (2000 lines)... I was no succes redirect these messages to file.

[Santiago]

"I got crash when I play with Pwmleds. Normaly it works fain, but when i do
more (about 6-8) cycles of the Play - Reload - Play - Reload - etc"

Yes... there is a problem when some Play-Reload cycles are executed... but never crashed for me,
Looks like this happens when using timer0, But not sure yet. Perhaps is just when using Timer0+interrupts.

Perhaps the crash is due Gpsim-0.22, in 0.24 the problem persist, but ktl doesn't crash (for me)

"attempt write to invalid file register
address 0x1a2, value 0x0"

This error is a Gpsin-0.22 problem, perhaps you got crash just because 0.22.

[Anonymous]

"Perhaps the crash is due Gpsim-0.22, in 0.24 the problem persist, but ktl doesn't crash (for me)"

yes, it is possible reason, i think this, but to make sure (and for others) i wrote this here. I will close this bug.