as i understand the code, the sony_arw_load_raw() function uses the BAYER(row,col) macro to write to a VMA region and the calculated offset is out of range.. I think this happens because the size given in the header of the arw file isn´t right because some part of the arw file is missing.. because libraw/dcraw uses the header information it tries to write / read to a area which is outside the mmaped area. But i just guessed the later.
I can´t find a specification of the sony .arw file format / header format on the net, to check the damaged file for possible differences in header / content information...
as i understand the code, the sony_arw_load_raw() function uses the BAYER(row,col) macro to write to a VMA region and the calculated offset is out of range.. I think this happens because the size given in the header of the arw file isn´t right because some part of the arw file is missing.. because libraw/dcraw uses the header information it tries to write / read to a area which is outside the mmaped area. But i just guessed the later.
I can´t find a specification of the sony .arw file format / header format on the net, to check the damaged file for possible differences in header / content information...