Hi Andreas,
On 09/26/2017 10:08 PM, Andreas Tille wrote:
> I need to admit I have no idea why
>
> fseeko() on reference file: Invalid argument
>
> is happening on some architectures.
According to the manpage of fseek(), which is identical to fseeko()
apart from the offset data type:
ERRORS
[...]
EINVAL The whence argument to fseek() was not SEEK_SET,
SEEK_END, or SEEK_CUR. Or: the resulting file offset would
be negative.
I suspect that something is calling fseeko() with a negative offset.
I'd recommend doing an strace on the specific test binary that
fails on a porterbox (e.g. armhf) + on amd64 for comparison and
then look for the offending fseeko() call. That might help isolate
the issue.
Regards,
Christian
