You explained -- just not strongly enough to make me understand.
It takes hours of testing to generate a stack trace, but I wrote down
the most import part -- the last two frames. And it's very difficult to
get a clip for reproduction, as this is a live stream running for hours.
To be honest, I think the description is adequate. Anyone that knows
the H264 code should be able to determine quickly whether the report is
valid or not....
Mark
On 6/21/2013 1:17 AM, Carl Eugen Hoyos wrote:
Carl Eugen Hoyos <cehoyos@...> writes:
Mark Stevans <mark39518 <at> ...> writes:
When playing unreliable H264 streams with FFPlay, I
seem to get core-dumps randomly every few hours.
This sounds important, please provide the necessary
information as explained on
http://ffmpeg.org/bugreports.html
I apparently forgot to explain that it makes no sense
to open a ticket if you can neither provide the
necessary information as explained on
http://ffmpeg.org/bugreports.html nor a sample.
A sample would be useful (the size limitation
mentioned in above page is irrelevant in this case),
you may also only upload a sample, a developer will
probably look at it (every crash is important).
If you want comments on your patch, use
git format-patch and send the commit to ffmpeg-devel
where patches are discussed.
I apparently forgot to explain that it makes no
sense to post patches on the bug tracker, they
are usually ignored there.
Sorry, Carl Eugen
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
