Buffering should truncate if read() returns 0 since it's not a valid return there...
commit6cbfee4982f60d500e45a712a04d5132650d2e22
authorjethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657>
Mon, 21 Mar 2011 15:57:07 +0000 (21 15:57 +0000)
committerjethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657>
Mon, 21 Mar 2011 15:57:07 +0000 (21 15:57 +0000)
tree5a723851b47131c9eb226247d12bc3a53a017211
parent99590e293cb4435fd326aca11be67277a28de5e6
Buffering should truncate if read() returns 0 since it's not a valid return there as there should be data left to read. The loop wouldn't break until there was a message in the queue. I just experienced the case with crosslinked files and read stopped making progress, returning 0 each time it was called.

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@29626 a1c6a512-1295-4272-9138-f99709370657
apps/buffering.c