Bug in post scriptum parser y_offset #50
Comments
Merged
aminophen
added a commit
to TeX-Live/texlive-source
that referenced
this issue
Jan 8, 2023
* Changed files (on https://github.com/jlaurens/synctex): synctex_parser.c synctex_parser_readme.md synctex_parser_utils.c - Fix compilation with clang with -Wformat-nonliteral. jlaurens/synctex#38 - Fix build when compiling with -Werror=implicit-function-declaration. jlaurens/synctex#39 - More explanations. - Remove recursion form _synctex_free_handle_old. - Fix a Bug in post scriptum parser y_offset. jlaurens/synctex#50 The following issue is not resolved: - Fix a Memory leak when opening files. jlaurens/synctex#49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Line 4564 of synctex_parser.c (towards end of _synctex_scan_post_scriptum function) should read:
instead of x_offset.
Because scanner->y_offset and scanner->y_offset are initialised to the bogus value 6.027e23, setting any X or Y offset in the post scriptum leads to synctex applying a y_offset of 6.027e23. So this bug breaks the post scriptum offset override feature, leading to bogus output from synctex view/edit if any offset is set.
The text was updated successfully, but these errors were encountered: