summaryrefslogtreecommitdiff
path: root/gst-plugins-good.doap
diff options
context:
space:
mode:
authorTim-Philipp Müller <tim@centricular.com>2021-05-29 12:54:22 +0100
committerTim-Philipp Müller <tim@centricular.com>2021-05-29 14:31:34 +0100
commitaa4448cdd6b59bce0c0bd925ca56901f58a572e2 (patch)
tree9ffef0b4a2649e9e125df791093f29313b4e0f78 /gst-plugins-good.doap
parentf4049fc292ce1ed749701d2a31bf6026b7d60eac (diff)
downloadgstreamer-plugins-good-aa4448cdd6b59bce0c0bd925ca56901f58a572e2.tar.gz
rtpjpegpay: fix image corruption when compiled with MSVC on Windows
On Windows with MSVC, jpeg_header_size would end up 2 bytes larger than it should be. This then leads to the first 2 bytes of the actual jpeg image data to be dropped, because we think those belong to the header, which results in an undecodable image when reconstructed in the depayloader. What happens is that when the compiler evaluates jpeg_header_size = mem.offset + read_u16_and_inc_offset_by_2(&mem); it actually uses the mem.offset value after it has been increased by the function call on the right hand size of the equation. From section 6.5 of the C99 spec: 3. The grouping of operators and operands is indicated by the syntax [74]. Except as specified later (for the function-call (), &&, ||, ?:, and comma operators), the order of evaluation of subexpressions and the order in which side effects take place are both unspecified. Fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/889 Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/merge_requests/999>
Diffstat (limited to 'gst-plugins-good.doap')
0 files changed, 0 insertions, 0 deletions