You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Primarily for debugging the "dancing" gif, show how many pixels were decoding for each image data block. Don't just put a printf in the gd code, as that mucks up the test output. Good place to put it is in the gd_main_t or gd_info_t, although the latter is a bit too deep.
the output length is updated in gd_image_expand_code
the block type event is GD_BLOCK_IMAGE_DATA, after the call to gd_read_image_data
The spec would go in either:
image_block_spec.cc
read_block_error_spec.cc
read_block_spec.cc
The text was updated successfully, but these errors were encountered:
Maybe better is read_bblock_spec.cc. It references gd_init() and gd_read_image_data(). However, the latter is currently only checking the correct bytes are read from the mock file, in the "image data" spec.
Almost fixed, but mushroomed into fixing the error handlers. Could not run the whole 128px gif because the string table ran iut of space for entries and string. That required a major refactor, including tests..
Primarily for debugging the "dancing" gif, show how many pixels were decoding for each image data block. Don't just put a printf in the gd code, as that mucks up the test output. Good place to put it is in the gd_main_t or gd_info_t, although the latter is a bit too deep.
The spec would go in either:
The text was updated successfully, but these errors were encountered: