From 38a9a96f12c6e309ad13d80ad67eca1c656a0bf4 Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Thu, 3 Sep 2020 20:43:15 +0000 Subject: Fix two issues with .po (page offset) formatting: 1. Truncate excessive offsets to a width reasonable in the context of manual pages instead of printing excessively long lines and sometimes causing assertion failures; found in an afl run performed by Jan Schreiber . 2. Remember both the requested and the applied page offset; otherwise, subtracting an excessive width, then adding it again, would end up with an incorrectly large offset. While here, simplify the code by reverting the previous offset up front, and also add some comments to make the general ideas easier to understand. --- regress/roff/po/range.out_ascii | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 regress/roff/po/range.out_ascii (limited to 'regress/roff/po/range.out_ascii') diff --git a/regress/roff/po/range.out_ascii b/regress/roff/po/range.out_ascii new file mode 100644 index 00000000..cc55df27 --- /dev/null +++ b/regress/roff/po/range.out_ascii @@ -0,0 +1,19 @@ +PO-RANGE(1) General Commands Manual PO-RANGE(1) + +NNAAMMEE + ppoo--rraannggee - page offsets out of range + +DDEESSCCRRIIPPTTIIOONN + initial text + +too small + + back in range + + too large + + back in range + + final text + +OpenBSD September 3, 2020 OpenBSD -- cgit