Michael Niedermayer <[EMAIL PROTECTED]> added the comment: On Sat, Jul 19, 2008 at 07:49:55AM +1000, Michael O wrote: > This is rather surreal. > > I submitted a bug report with a clear description of the problem, and > a fix for it. > > The current code is _obviously_ wrong. Accessing memory before the > start of the buffer is always wrong. > > The crash is randomly trigger by any interlaced high definition H.264 > content. You don't need the specific (very, very large) files that I > have. > > I've tried on numerous occasions to try and update this ticket, but > the issue tracker is permanently broken as far as I can see; It's > _never_ accepted an email update in 3 months of trying.
It seems this reply has reached the tracker, for the others, pester luca (see CC), he is also the one to pester for any other roundup problems. > > And then the end response to all this is no-one actually reading the > code and spotting the (obvious!) bug I pointed out, but instead > closing the ticket due to 'no response'. Well, The report, contains no gdb output (mandatory for crashes) no valgrind output (mandatory for memory issues) no patch (mandatory for any "fix") no sample file to reproduce it does contain some vague description of a crash and a bug that is not reproduceable. and a claim of an out of array access, which isnt out of the array as far as i can tell for ffmpeg and ffplay. It may be that the quoted code is wrong and that it is out of the allocated space for some applications. But honestly this is becoming quite a bit too speculative, especially considering that we have many well written bug reports which need to be dealt with. > > So here's my official "I give up". Do what you like. I've patched my > local version so it no longer crashes so I'm happy. Instead of whining (and being happy that your ffmpeg still crashes because hey i know there are more bugs in h264.c than this). Why not provide at least some information so we can fix it? if it really is reproduceable with any interlaced H.264 then iam sure you can just point to some existing file on the wide net that does reproduce it, if you dont want to upload one. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Breaking DRM is a little like attempting to break through a door even though the window is wide open and the only thing in the house is a bunch of things you dont want and which you would get tomorrow for free anyway ______________________________________________________ FFmpeg issue tracker <[EMAIL PROTECTED]> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue427> ______________________________________________________
