Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opj_skip_from_file error #314

Closed
gcode-importer opened this issue Mar 25, 2014 · 6 comments
Closed

opj_skip_from_file error #314

gcode-importer opened this issue Mar 25, 2014 · 6 comments

Comments

@gcode-importer
Copy link

Originally reported on Google Code with ID 314

In openjpeg.c the function opj_skip_from_file passes the number of bytes as an OPJ_OFF_T
which is 8 bytes,
but the parameter of the standard FSEEK function is a long which is 4 bytes.

As a consequence, the WHENCE parameter is taken in the second part of the 8 bytes,
and is 0,
which means SEEK_SET, instead of SEEK_CUR.

The final result is that the function opj_jp2_skip_jp2c  positions the file at address
8 instead of
skipping 8  bytes from current position.

Reported by cutanet.dev on 2014-03-25 15:00:19

@gcode-importer
Copy link
Author

You are either using a brain dead compiler or are using weird compilation flags. In
both case we are missing information to actually determine why cmake introspection
mecanism failed in your case. Closing as invalid.

Reported by malaterre on 2014-03-25 15:43:34

  • Status changed: Invalid

@gcode-importer
Copy link
Author

I have spent two hours investigating the problem to see where it comes from. I dont
appreciate that you merely dismiss the issue as invalid. I just compiled the sources
with the standard commands, and do not use weird compile flags. There is obviously
a problem somewhere since OPJ_OFF_T is ALWAYS defined as 64bits in the source of openjpeg.h,
 even where the operating system uses 32bits addresses...


Reported by cutanet.dev on 2014-03-25 17:00:05

@gcode-importer
Copy link
Author

That was my goal here. With this comment, I am sure that in a few dozens iterations,
I'll be able to have a proper bug report (openjpeg version, compiler version, system
version, exact command line used, strace output, valgrind output...). So I'll continue
being extremely rude, of course if you were to give me those infos in the first place
this would have been a lot less fun of course.

Reported by malaterre on 2014-03-25 17:04:02

@gcode-importer
Copy link
Author

I have fixed the problem for myself.  Just wait for another user reaching the problem
to have it again in your issue list.

Reported by cutanet.dev on 2014-03-25 17:08:51

@gcode-importer
Copy link
Author

Reported by malaterre on 2014-03-26 14:57:51

  • Status changed: Accepted

@gcode-importer
Copy link
Author

Reported by malaterre on 2014-03-26 14:58:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants