[FFmpeg-devel] [PATCH] Checked get_bits.h functions to prevent overread
michaelni at gmx.at
Fri Sep 9 14:49:09 CEST 2011
On Fri, Sep 09, 2011 at 02:41:18PM +0200, Michael Niedermayer wrote:
> On Fri, Sep 09, 2011 at 12:03:40PM +0200, Laurent Aimar wrote:
> > On Fri, Sep 09, 2011 at 09:46:34AM +0000, Carl Eugen Hoyos wrote:
> > > Laurent Aimar <fenrir <at> elivagar.org> writes:
> > >
> > > > > > I have a list of crashes with their backtraces. A lot of the files used
> > > > > > comes from VLC and mplayer FTP and so will probably be easy to retreive.
> > > > >
> > > > > > Is sending it to the ML is the right choice ?
> > > > >
> > > > > What's wrong with opening a ticket as explained on
> > > > > http://ffmpeg.org/bugreports.html?
> > > >
> > > > It depends. I can create a unique ticket for the backtrace I have
> > >
> > > That would be great! (or do you mean you could but it is too much effort?)
> > I meant that I have no problem creating a few tickets if that's what would be
> > usefull for ffmpeg but it would be too much work for me to create a ticket for
> > each crash.
> > Also, as the bug tracker is probably public, I can also simply send the list
> > first to this ML and then we can work from that ?
> yes, or maybe better open a single ticket with the list and this can
> then over time be split up into multiple tickets.
More elaborately, my idea is
* open a single ticket
* people try to fix issues in this and the list shortens significantly
* some change in the bitstream reader of speed uncritical "fringe"
codecs again possibly shortens it significantly
* what remains is split up based on previous work into groups of
likely duplicate crashes
This of course doesnt have to happen in this order
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
DNS cache poisoning attacks, popular search engine, Google internet authority
dont be evil, please
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the ffmpeg-devel