YAM crashed when I pressed Delete key in Ediitor window whilst HD LED flashed

This is a known bug of TextEditor.mcc. Unfortunately I haven't been able to track it down to a point where I can tell for sure what is causing the crash. It finally happens in newlib.library, but the last code location of TE.mcc as pointed out by the crashlog does not contain a suitable function call.

I hope Jörg Strohmayer can help us.

I just built a test version of TextEditor.mcc with some enhanced limit checks in the crashing function. I cannot tell if this really fixes the crashes, but at least I hope it does. Please give it a try and report back here. Please note that the version number and date is the same as for the last official release, so don't mix these up.

Thanks for this. I don't know how I will go repeating it as the crash was in a rare situation. Guess I could just use brute force on my delete key to see if there is a reaction but that's not practical.

Replying to hypexed@…:

Thanks for this. I don't know how I will go repeating it as the crash was in a rare situation. Guess I could just use brute force on my delete key to see if there is a reaction but that's not practical.

I very much doubt that the DEL key is the only one to trigger this bug. For me happens with any key, but unfortunately about 3 times per year only. This is a quite weak basis to search for a bug. Especially when the crash log does not point to a sensible position.

I just attached a new version of TextEditor.mcc (now with a bumped date at least) which contains some recent fixes. I very much assume TextEditor.mcc to either trash memory or to operate on memory outside the allocated range which finally makes newlib.library go crazy.

TextEditor.mcc 15.38 (12.7.2012)

Any new crashes with the (hopefully) fixed TE.mcc?

Bump!

Hi. I haven't had any further crashes. I will test the newer version also. Somethhng that may be of interest, I do get the following from the first TE you attached:

../include/mccinit.c:968:LibInit(TextEditor.mcc)
** TextEditor.mcc v15.38 startup **********************
Exec version: v53.25
Initializing runtime debugging:
set debug classes/flags (env:texteditor.mcc.debug): 000000f6/00000003
** Normal processing follows ***************************************
../include/mccinit.c:1133:LibOpen(TextEditor.mcc): 0
../include/mccinit.c:1272:MCC_Query(TextEditor.mcc): 0
../include/mccinit.c:1133:LibOpen(TextEditor.mcc): 1
../include/mccinit.c:1272:MCC_Query(TextEditor.mcc): 0
../include/mccinit.c:1211:LibClose(TextEditor.mcc): 2
../include/mccinit.c:1133:LibOpen(TextEditor.mcc): 1
../include/mccinit.c:1272:MCC_Query(TextEditor.mcc): 0
    InitConfig.c:98:couldn't get config item: 0xad00005f
    InitConfig.c:98:couldn't get config item: 0xad000054
    InitConfig.c:98:couldn't get config item: 0xad000055
    InitConfig.c:98:couldn't get config item: 0xad000059
    InitConfig.c:98:couldn't get config item: 0xad00005a
    InitConfig.c:98:couldn't get config item: 0xad000066
    InitConfig.c:98:couldn't get config item: 0xad000067
    InitConfig.c:98:couldn't get config item: 0xad00006b
   InitConfig.c:98:couldn't get config item: 0xad000055
../include/mccinit.c:1089:LibExpunge(TextEditor.mcc): 2
../include/mccinit.c:1089:LibExpunge(TextEditor.mcc): 2
../include/mccinit.c:1089:LibExpunge(TextEditor.mcc): 2
../include/mccinit.c:1089:LibExpunge(TextEditor.mcc): 2
  InitConfig.c:98:couldn't get config item: 0xad000055
           BlockOperators.c:627:text = 0x557e2818 "

That is just standard debug output generated by TextEditor.mcc. Or are you referring to anything "bad" within there?

No, nothing bad, but the "couldn't get config item:" lines did concern me.

That message only means that TE.mcc uses its default value, because there was no custom setting found in the configuration.

This bug should be fixed with the recently release TextEditor.mcc 15.39. If it happens again, then please reopen this ticket.

Thanks. That's good to know.