That's a Canon task. This doesn't say much about where the bug is:
- it can be a Canon bug (remember that raw is a debug flag in their code, so it probably didn't get as much test coverage as the stuff that got enabled in the final version)
- or it can be a ML bug (since both run in the same memory space, it's easy for one task to write over the other's data structures)
So, a user-level program can access the entire RAM (you probably already know this). It's a double-edged sword: it makes it very easy for ML to boot and patch things around, but combine this with
a poor design decision from Canon regarding persistent settings and you'll understand why this kind of error is very dangerous and should be fixed asap.
Of course, the probability of something going wrong is very low. Some of my neighbours used a WW2 projectile for 10 years as
anvil and they are still alive
Back to our topic: if you enable some raw histograms in photo mode (say raw zebras), and autofocus, can you trigger the problem?
Another test: in boot-hack.c, my_big_init_task, do just this:
static void my_big_init_task()
{
call("lv_save_raw", 1);
}
and in gui.c, comment out the TASK_OVERRIDE line (at the end).
With this change, you will have no user tasks running, just plain Canon firmware in RAW LV mode. If you are still getting the error, it's a Canon bug (but we still have to find some workaround).
