i looked at the new code live.2008.07.24. i feel there is one issue.
Now QuickTimeFileSink constructor is opening the file using
OpenOutputFile but it is not checking the return value. If file open
fails the filehandle will be NULL and may give core dump wherever
filehandle is used.
I feel prev
Hi Ross,
i looked at the new code live.2008.07.24. i feel there is one issue. Now
QuickTimeFileSink constructor is opening the file using OpenOutputFile but
it is not checking the return value. If file open fails the filehandle will
be NULL and may give core dump wherever filehandle is used.
I feel
Thanks for the bug report. This will be fixed in the next released
version of the software.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinf
Hi Ross,
it looks there is a bug in QuickTimeFileSink. The
QuickTimeFileSink::completeOutputFile() is not closing the file handle.
(This error will come if user uses different files for saving the stream
other than stdout, stderr)
Because of the above bug, creating new file using "OpenOutputFile"
