Bug Reports against Recent Builds -- Report bugs here - page 27 - CHDK Releases - CHDK Forum  
« previous next »
Pages: 1 ... 22 23 24 25 26 [27] 28 29   Go Down

Bug Reports against Recent Builds -- Report bugs here

  • 281 Replies
  • 78815 Views
*

Online reyalp

  • ******
  • 12174
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #260 on: 02 / November / 2014, 17:44:41 »
Advertisements
Code: [Select]
___> !vlog=require'extras/vxromlog'
___> !l=vlog.load('s3ROMLOG_ptpconnect.LOG')
___> !l:print()
Assert ZoomLensController.c line 489
Occured at 2014:11:02 20:22:09
Task ID: 3145144
Task Name: tSpyTask
Stack:
0xff813ba4     -8307804
0x00000000            0
0xffae7700     -5343488
0x00000000            0
0x02000000     33554432
0x00000000            0
0xffaf2154     -5299884
0xffaf26ec     -5298452
0x00000000            0
0xff829a1c     -8218084
0xfffffffd           -3
0x00000000            0
0x00540000      5505024
0x04000000     67108864
0x00000000            0
0x002ffc1c      3144732
0x00000200          512
0x002ffc62      3144802
0xffaf1d00     -5300992
0x00000000            0
0x002ffc60      3144800
0x0006c884       444548
0x002ffc66      3144806
0xffffffff           -1
0xffffffff           -1
0x0b08ffff    185139199
0xffffff02         -254
0xffffffff           -1
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4039
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #261 on: 02 / November / 2014, 17:48:09 »
Quote from: philmoz on 02 / November / 2014, 17:23:37
Can you decode the binary romlog and post it please?

The 'bad' config has module logging enabled, perhaps there's a problem with that - I can't see any other differences in the config files that might explain a crash.
Attached a decoded version (created with chdkptp), plus modules.log, lua.flt.

edit: reyalp was faster

edit2:
Enabling module logging on a clean config does not bring back the problem.
« Last Edit: 02 / November / 2014, 18:04:04 by srsa_4c »
Logged
*

Online reyalp

  • ******
  • 12174
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #262 on: 02 / November / 2014, 18:06:54 »
Odd the crash is in ZoomLensController.c

The assert is in sub_FFAE76C0, which is called by an event proc called GetCurrentZoomLensDirection, among other things.

The stack trace doesn't contain any CHDK code references that I see.

I don't think CHDK should be doing anything with zoom on startup.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4039
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #263 on: 02 / November / 2014, 18:57:02 »
Great. I have copied the affected card's CHDK directory (including the bad config) to another card - no problem with ptp... It only happens on that particular card (it's 4GB, half-filled with pictures and videos). It makes no sense to continue the search, thanks for your efforts.
Whatever the reason (I suspect RAM corrupted by either the firmware or CHDK or a hw fault), these now seem to be real possibilities...
Logged
*

Offline philmoz

  • *****
  • 3133
    • Photos
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #264 on: 02 / November / 2014, 19:27:25 »
Quote from: srsa_4c on 02 / November / 2014, 18:57:02
Great. I have copied the affected card's CHDK directory (including the bad config) to another card - no problem with ptp... It only happens on that particular card (it's 4GB, half-filled with pictures and videos). It makes no sense to continue the search, thanks for your efforts.
Whatever the reason (I suspect RAM corrupted by either the firmware or CHDK or a hw fault), these now seem to be real possibilities...

What if you copy the entire contents of the card?
Could be a startup timing issue with the half full card - presumably the firmware is indexing the images & videos on startup.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
*

Online reyalp

  • ******
  • 12174
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #265 on: 02 / November / 2014, 20:04:29 »
Assuming the TCB structures aren't totally hosed, this should originate from a call in CHDK code since the assert is in spytask.

@srsa: The crash actually happens when you connect the USB cable, or connect chdkptp?

An oddity in the camera log:
Code: [Select]
00007020: ConnectUSBCable
00007020: CmrConState_CheckStoreLens
00007020: _Init_PcConnect
00007020: CmrCon_DeliverUSBConnect
00007020: _ConnectUSBCBR
00007020: LogicalEvent:0x3137:adr:0x0,Para:0
00007030: LogicalEvent:0x5005:adr:0x0,Para:0
00007090: PTPRspnd.StartUpPTPFrameworkClient
00018470: Window:IneffectiveLockPhysicalScreen
The last message is some 11 seconds after the USB cable connection.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4039
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #266 on: 03 / November / 2014, 19:41:54 »
Quote from: philmoz on 02 / November / 2014, 19:27:25
Could be a startup timing issue with the half full card - presumably the firmware is indexing the images & videos on startup.
I was suspecting this first so I then waited for a while before connecting with ptp (thus the 10+ second delay before the last log entry).

Quote from: reyalp on 02 / November / 2014, 20:04:29
@srsa: The crash actually happens when you connect the USB cable, or connect chdkptp?
When I attempt a connection in chdkptp.

I'll probably continue investigating this.
Logged
*

Online reyalp

  • ******
  • 12174
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #267 on: 03 / November / 2014, 23:35:50 »
Quote from: srsa_4c on 03 / November / 2014, 19:41:54
When I attempt a connection in chdkptp.

I'll probably continue investigating this.
This is peculiar, since SpyTask shouldn't really know about a ptp connection at all. The only thing I can think of is something related to the OSD trying to update (read the zoom position maybe?)

You might be able to get more info in the romlog using some LogPrintfs, but I'm not sure where you'd put them.
Logged
Don't forget what the H stands for.
*

Offline ADamb

  • **
  • 65
  • sx200is
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #268 on: 04 / November / 2014, 14:01:47 »
Snake (games) is eating background  :D
Is it bug or feature?
IMHO draw_filled_rect should have color definitions by MAKE_COLOR.
Logged
SX200 IS-100C
*

Offline srsa_4c

  • ******
  • 4039
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #269 on: 08 / November / 2014, 16:52:41 »
Quote from: reyalp on 03 / November / 2014, 23:35:50
This is peculiar, since SpyTask shouldn't really know about a ptp connection at all. The only thing I can think of is something related to the OSD trying to update
I managed to catch more information by using a custom assert handler. It now looks like the bug is in the port. The port's lens_get_focus_pos_from_lens() implementation enables calling the fw's GetFocusLensSubjectDistanceFromLens function when camera_info.state.state_kbd_script_run is true. The function wanting to know the subject distance is shooting_update_dof_values(). So, the crash is triggered when the DOF display is enabled and a script is executed in playback mode. PTP is not related.
Logged
Pages: 1 ... 22 23 24 25 26 [27] 28 29   Go Up
« previous next »
 

Related Topics