MP4ReadProvider still causes direct call to stat64
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
What steps will reproduce the problem?
1. use mp4readprovider with custom open/read/seek/close implementations
2. do NOT use a file in the underlying file system (hence custom impls)
3. mp4v2 calls stat64 (according to strace) on the non-existing file and then
fails to open the file (presumably because it doesn't get the file size)
What is the expected output? What do you see instead?
I had hoped you'd just run assuming 'infinite' file size until read fails;
alternatively, you need to modify the API to allow me to also provide a 'stat'
replacement.
What version of the product are you using? On what operating system?
2.0.0, Debian.
Please provide any additional information below.
I was trying to use MP4v2 in GNU libextractor.
Original issue reported on code.google.com by groth...@gmail.com
on 23 Aug 2012 at 9:24
Google Code Exporter commented
Totally agree; this is something about the read/writer provider interfaces that
I've found nonsensical; open/read/seek/close is available, but not file size of
all things.
Original comment by kid...@gmail.com
on 1 Oct 2012 at 2:38
- Changed state: Accepted