[libav-bugs] [Bug 1103] New: rtsp: noop in parse_rtsp_message interpreted as EOF (unless reply already had an error)

bugzilla at libav.org bugzilla at libav.org
Wed Nov 29 19:16:49 CET 2017


https://bugzilla.libav.org/show_bug.cgi?id=1103

            Bug ID: 1103
           Summary: rtsp: noop in parse_rtsp_message interpreted as EOF
                    (unless reply already had an error)
           Product: Libav
           Version: git HEAD
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: ---
         Component: libavformat
          Assignee: bugzilla at libav.org
          Reporter: tmatth at videolan.org

Not entirely sure that this is a bug, but upon receiving an RTSP OPTIONS
message when using -rtsp_transport udp, both avplay and avconv will call
parse_rtsp_message which returns 0 if no error occured [1].
Further up the call chain in read_packet, this is interpreted as an EOF [2][3],
prompting avplay and avconv to exit, even though media is still being streamed.
Would it make sense to have parse_rtsp_message return something else, or to
otherwise isolate the EOF case from the non-error case?

[1]
https://git.libav.org/?p=libav.git;a=blob;f=libavformat/rtsp.c;h=17a25a310ecd2a35125c672d533b0e42a3b7c9a5;hb=HEAD#l1934
[2]
https://git.libav.org/?p=libav.git;a=blob;f=libavformat/rtsp.c;h=17a25a310ecd2a35125c672d533b0e42a3b7c9a5;hb=HEAD#l2071
[3]
https://git.libav.org/?p=libav.git;a=blob;f=libavformat/rtsp.c;h=17a25a310ecd2a35125c672d533b0e42a3b7c9a5;hb=HEAD#l2087

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.libav.org/pipermail/libav-bugs/attachments/20171129/01dbced4/attachment.html>


More information about the libav-bugs mailing list