Obviously, the cam needs to be able to survive until you have the chance executing the ShowCameraLog eventproc.
You should also get the recent messages if it crashes with a romlog. My current "big camera log" command is
=call_event_proc('StopCameraLog') sleep(200) call_event_proc('StartCameraLog',0x20,0x6000) sleep(100) require'uartr'.start('A/test.log',true,0x8000)
(difference from one you linked is that it enlarges the uart log buffer as well as the camera log, which avoids losing data in some cases)
@asm1989
In general, for this kind of situation I would try to get capt_seq running without any of the hooks enabled first. Scripted shoot() will not work correctly if the raw hook isn't present, but you should be able to shoot with scripted or physical button presses.
You do need to watch to make sure the debugging code itself isn't clobbering anything. I think my code is OK, but differences in your firmware could make it unsafe. You can comment out the debug logs in areas that you aren't working on too.
regarding
"loc_fc0b2706:\n"
" bl sub_fc0b3d4a\n"
" b loc_fc0b27f0\n"
" beq loc_fc0b2740\n"
" movs r3, r0\n" // this was no it g7x mabe like removed literal at fc1502ba in gx7 needs check
" ldm r6!, {r3}\n"
" movs r3, r0\n"
" pop {r6}\n"
" movs r0, r0\n"
"loc_fc0b2718:\n"
I would say the canon literal pool started at the beq ... because there is no way it could be reached, and the following instructions make little sense. I don't think this is the cause of your crash, but this kind of thing could cause the immediately following disassembly to be incorrect so it's better to be sure.
Looking at the raw values, the beq through movs r0,r0 are
0003d018
0003ce08
0000bc40
which are all constants that appear in ldr instructions (3d018 not in that function, but nearby), so it does look like those 6 are a literal pool. Since the following is jumptable target, it must be actual code.
Regarding
" bne loc_fc0f24f8_new\n" /// added _new to build
I'm not clear what this is about, you shouldn't need to add _new? If using just "loc_fc0f24f8" caused some problem, there is something wrong which needs to be investigated.