Note: the suggested modification in #271 (comment) in lines 242++ has not been applied. These lines of code concern data that is not necessarily followed by "data blocks" that can be skipped this way. The original file bug.gif issues the following warnings:

bug.gif: unknown GIF code 0x73 at offset 13
bug.gif: unknown GIF code 0x6c at offset 14
bug.gif: unknown GIF code 0x61 at offset 15
bug.gif: unknown GIF code 0x6a at offset 16
bug.gif: unknown GIF code 0x64 at offset 17
bug.gif: unknown GIF code 0x6c at offset 18
bug.gif: unknown GIF code 0x6b at offset 19
bug.gif: unknown GIF code 0x73 at offset 20
bug.gif: unknown GIF code 0x61 at offset 21
bug.gif: unknown GIF code 0x6a at offset 22
bug.gif: unknown GIF code 0x64 at offset 23
bug.gif: unknown GIF code 0x6b at offset 24
bug.gif: unknown GIF code 0x6c at offset 25
bug.gif: unknown GIF code 0x6a at offset 26
bug.gif: unknown GIF code 0x6b at offset 27
bug.gif: unknown GIF code 0x6b at offset 28
[229] Fl_GIF_Image: bug.gif - unexpected EOF or read error at offset 29

Hint: interpreting GIF code 0x73 as a block size would cause a read error and obfuscate better error diagnostics. IMHO there's nothing we can do in such a case.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.