5d2 crash log000.log of any interest? May be related to over-heating ... or not?

[l_d_allan]

Nightly build: Jan 28, 2015

If it is of interest, here are the contents of:
CRASH00.LOG

Code Select Expand

ASSERT: 0
at KernelDry\KerSem.c:306, task Fread
lv:0 mode:3


Magic Lantern version : Nightly.2015Jan29.5D2212
Mercurial changeset   : 703ee626326d (unified) tip
Built on 2015-01-28 23:10:03 UTC by [email protected].
Free Memory  : 128K + 3991K

and ...
log000.log
... difficult to copy/paste ... has null codes embedded in log000.log on almost every line ...
I can try again and make more of an effort to maybe replace null codes if it would help.

Code Select Expand

58th (of 3189 lines)
1524: 13169.205 [LVCFG] PROP_EFIC_TEMP 9

The camera had only been on several minutes at the most ... and not in LiveMode.

If helpful, I can open a "Bug Report".

It does seem like a possible bug to have the format of log000.log have lines with the format of ...

Code Select Expand

null-code contents \n
null-code contents \n
.....
null-code contents \n


[a1ex]

If you find a way to reproduce the error, then yes, it is of interest.

[l_d_allan]

It seems unlikely to show up again. I use the older 5d2 less than my newer 6d. Also, it was with an somewhat older Nightly Build ... although the related code would seem unlikely to have changed.

I would suggest thinking about changing how the log###.log file is written out. I don't know what the issues are, but I have some doubts that you really want a null byte after the CR-LR \n.  For my situation (using Windows), that made it difficult to cut/paste the contents of log000.log.