Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bugs
  • Category Operating System/Drivers
  • Assigned To
    mcuelenaere
  • Operating System Another
  • Severity Medium
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by mcuelenaere - 2010-02-16
Last edited by mcuelenaere - 2010-02-21

FS#11028 - r24657 breaks MIPS builds

r24657 breaks MIPS-based players (Onda VX747, VX777) with an Address Exception (Store) in sab_process_dir()

Closed by  mcuelenaere
2010-02-21 23:00
Reason for closing:  Fixed
Additional comments about closing:  

In r24835.

I haven’t figured this out yet, looks like this isn’t an unaligned pointer problem but a NULL pointer dereference.

Assembly of crash at 0x8005BC84: http://pastebin.com/m2b403c87 (a0 contains 0×0).
For some reason the hardware says the referenced address is 0×140 while it should be (0×0+0×20) if I read the asm correctly..

Do you know to which line it corresponds on in the C code or do you have a way to know ?
Perhaps that’s a fat_dir alignement problem due to the fact that it uses buffers that are probably manipulated by the fat code but I’m really not sure.
Could you also try with the next commit I did to dircache ? I finally move this fat_dir buffer to memory so this way we can make sure this is not an alignment problem.

Do you know to which line it corresponds on in the C code or do you have a way to know ?

That’s what I was trying to figure out yesterday, will look again today.

Could you also try with the next commit I did to dircache ?

Crashes at the same instruction (it still looks like the CPU is accessing address 0×140, but I can’t see why that happens..).

Any progress concerning this bug ?

Any progress concerning this bug ?

Nope, sorry; haven’t had much free time. I’ll try looking at this today..

I possibly solved the bug in r24835, I was doing a stupid NULL-pointer deference. That could explain this memory access to address 0×140 !
Could you try with this new commit ?

Yep, that seems to have fixed the issue! Thanks!

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing