help: how to debug script interrupting? - page 16 - General Discussion and Assistance - CHDK Forum

help: how to debug script interrupting?

  • 224 Replies
  • 58339 Views
*

Offline reyalp

  • ******
  • 14093
Re: help: how to debug script interrupting?
« Reply #150 on: 01 / May / 2013, 01:54:55 »
Advertisements
Running d10 in no shoot mode, with the 10ms sleep and buffered log has hit the error twice in less than an hour, after 1600 cycles.

So this seems like a valid and probably quicker way of finding out if a camera is affected by the bug.

For anyone who is interested, the attached patch is a minimal workaround to ignore the bug and log it to the script console. I haven't verified it, but the logic is the same as my debugging patch, with a slightly tighter restriction on the bad value. The patch is against the trunk, but it should apply to pretty much any chdk version.
Don't forget what the H stands for.

Re: help: how to debug script interrupting?
« Reply #151 on: 01 / May / 2013, 23:25:32 »
A1200 just ran for 12000 cycles (no shoot mode) before I got tired of listening to it.   
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14093
Re: help: how to debug script interrupting?
« Reply #152 on: 02 / May / 2013, 00:35:12 »
A1200 just ran for 12000 cycles (no shoot mode) before I got tired of listening to it.
What build did you use?

It's possible some aspect of this could be compiler dependent. I'm using the windows gcc4 environment from chdkshell
Code: [Select]
$ arm-elf-gcc --version
arm-elf-gcc.exe (GCC) 4.5.1
The autobuilds presumably also have the problem.
Don't forget what the H stands for.

Re: help: how to debug script interrupting?
« Reply #153 on: 02 / May / 2013, 00:39:12 »
What build did you use?
Build with the "hacki" linux build environment he shared last year.
Code: [Select]
arm-elf-gcc (GCC) 4.4.3Unless he has changed it,  I think it's the autobuild toolchain / environment?

Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline reyalp

  • ******
  • 14093
Re: help: how to debug script interrupting?
« Reply #154 on: 02 / May / 2013, 01:00:48 »
Build with the "hacki" linux build environment he shared last year.
Code: [Select]
arm-elf-gcc (GCC) 4.4.3Unless he has changed it,  I think it's the autobuild toolchain / environment?
I expect so, doubt he's changed it.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4451
Re: help: how to debug script interrupting?
« Reply #155 on: 02 / May / 2013, 13:36:23 »
A1200 just ran for 12000 cycles (no shoot mode) before I got tired of listening to it.
Similar on the a3200 (10k cycles without shooting, in AF lock, no error). Note that the a3200 and a1200 are from the same camera generation (r47).

However, I got an error in 850 cycles on the ixus110_sd960 (r31, same generation as the d10). Perhaps we should collect the affected and (presumably) not affected models somewhere, maybe there's a pattern.

I'm using a gcc 4.5.1 based toolchain (linux, 32bit) from the CHDK-DE site.

Re: help: how to debug script interrupting?
« Reply #156 on: 02 / May / 2013, 14:20:55 »
Perhaps we should collect the affected and (presumably) not affected models somewhere, maybe there's a pattern.
I'll try it on my IXUS120_SD940 (r39) & G10 (r31).   Not sure I want to put the wear & tear on my borrowed SX50 just yet though.
« Last Edit: 02 / May / 2013, 14:23:50 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 4451
Re: help: how to debug script interrupting?
« Reply #157 on: 02 / May / 2013, 14:45:50 »
I'll try it on my IXUS120_SD940 (r39) & G10 (r31).   Not sure I want to put the wear & tear on my borrowed SX50 just yet though.
We already know that the SX50 is affected (thanks to lapser), you don't need to test it. To reduce wear, use AF lock, and disable shooting in the script settings (when using outslider's script).


Re: help: how to debug script interrupting?
« Reply #158 on: 02 / May / 2013, 14:53:02 »
I'll try it on my IXUS120_SD940 (r39) & G10 (r31).   Not sure I want to put the wear & tear on my borrowed SX50 just yet though.
We already know that the SX50 is affected (thanks to lapser), you don't need to test it. To reduce wear, use AF lock, and disable shooting in the script settings (when using outslider's script).
Yea - did that for the A1200.  Also turned off the AF assist lamp - it gets annoying after a while.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: help: how to debug script interrupting?
« Reply #159 on: 02 / May / 2013, 22:10:17 »
Perhaps we should collect the affected and (presumably) not affected models somewhere, maybe there's a pattern.
I'll try it on my IXUS120_SD940 (r39) & G10 (r31).   Not sure I want to put the wear & tear on my borrowed SX50 just yet though.
My G10 (aka The Black Tank) ran the 10K cycles in about 90 minutes with AF & AE lock (shooting off).  No crash.
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal