[FFmpeg-devel] [PATCH]Avoid overflows when reading pgm with maxval != 255 and 65535

Michael Niedermayer michaelni at gmx.at
Mon Jul 29 00:34:03 CEST 2013

On Sun, Jul 28, 2013 at 10:28:04PM +0000, Carl Eugen Hoyos wrote:
> Michael Niedermayer <michaelni <at> gmx.at> writes:
> > > The actual reason is that libjpeg v6b writes little 
> > > endian 16bit pgm files, the specification requires 
> > > big endian values.
> > 
> > i have realized this as well once i saw the commit 
> > fixing it in libjpeg
> I had fixed it in the release version myself before 
> I realised to test cvs...
> > this btw is easy to detect if we want to do it ...
> But isn't the work-around different on le and be?

> Note that it was always quite difficult to use 
> libjpeg to produce such files (neither distribution 
> nor standard compilation ever allowed it).

if such files couldnt be generated easily then it probably isnt worth
to add a workaround.
I assume you build libjpeg yourself to make such files ?

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Old school: Use the lowest level language in which you can solve the problem
New school: Use the highest level language in which the latest supercomputer
            can solve the problem without the user falling asleep waiting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20130729/bd980d08/attachment.asc>

More information about the ffmpeg-devel mailing list