Builder ffmpegsos-solaris10-sparc Build #12597

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpegsos-solaris10-sparc' triggered this build

Steps and Logfiles:

1. git update ( 12 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 0 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 0 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 14 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_sos.sh' failed ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Leo Izen

   leo.izenohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #252880

   Category	ffmpeg
   Changed by	Leo Izen <leo.izenohnoyoudont@gmail.com>
   Changed at	Sat 20 Dec 2025 17:53:21
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	105b6fcd9c5940a3fda1eddfef146055e0e24a3d

   Comments

   avcodec/exif: avoid leaking EXIF metadata upon parse failure
   Before this commit, exif_parse_ifd_list didn't free *ifd upon failure,
   relying on the caller to do so instead. We only guarded some of the
   calls against this function, not all of them, so sometimes it leaked.
   
   This commit fixes this, so exif_parse_ifd_list freeds *ifd upon failure
   so callers do not have to guard its invocation with a free wrapper.
   
   Fixes: ossfuzz 440747118: Integer-overflow in av_strerror
   
   Signed-off-by: Leo Izen <leo.izen@gmail.com>

   Changed files

   • libavcodec/exif.c

2. Change #252881

   Category	ffmpeg
   Changed by	Leo Izen <leo.izenohnoyoudont@gmail.com>
   Changed at	Sat 20 Dec 2025 17:53:23
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	784aa09fa8222f6704d953b5035f8d0f0bec1623

   Comments

   avcodec/exif: parse additional EXIF IFDs
   Most EXIF metadata is in IFD0 and most EXIF payloads only contain
   one IFD, but it is possible for there to be more IFDs after the
   existing trailing one. exiftool and similar software report these IFDs
   as IFD1, IFD2, etc. This commit reads those additional IFDs and attaches
   them as dummy entries in the top-level IFD ranging from 0xFFFC down to
   0xFFED, which are unused by the EXIF spec. The EXIF API is only able to
   return and work with a single IFD, so by attaching it as a subdirectory
   this metadata can be preserved.
   
   This is done transparently through the read/write process. Upon parsing
   an additional IFD1, it will be attached, but it will be written with
   av_exif_write after IFD0 rather than as a subdirectory, as intended.
   
   Existing files without more than one IFD, i.e. most files, will be unaffected
   by this change, as well as API clients looking to parse specific fields, but
   now more metadata is parsed and written, rather than simply being discarded
   as trailing data.
   
   Signed-off-by: Leo Izen <leo.izen@gmail.com>

   Changed files

   • libavcodec/exif.c
   • tests/ref/fate/exif-image-jpg
   • tests/ref/fate/exif-image-webp
   • tests/ref/fate/mov-heic-demux-still-image-multiple-thumb