summaryrefslogtreecommitdiffstats
path: root/stream
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-01-19 20:38:01 +0100
committerwm4 <wm4@nowhere>2014-01-19 21:15:55 +0100
commitef006dcae6b07a8abb7fed847fd4a9e647109584 (patch)
treef16cda83454b2e7d78a4d401ec9656a6003797d3 /stream
parent77e92bbb11ca6f8f94df1bf2c5bad997b114f02f (diff)
downloadmpv-ef006dcae6b07a8abb7fed847fd4a9e647109584.tar.bz2
mpv-ef006dcae6b07a8abb7fed847fd4a9e647109584.tar.xz
stream: print stream_read_line warnings by default
This is probably ok. Probing could hit this case very often, since it'll mean running this function on potentially binary data, but on the other hand, probing usually uses a memory stream (to limit the amount of data read), and memory streams have s->log silenced (details see open_memory_stream()).
Diffstat (limited to 'stream')
-rw-r--r--stream/stream.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/stream/stream.c b/stream/stream.c
index ad9987fc65..1caf6e718c 100644
--- a/stream/stream.c
+++ b/stream/stream.c
@@ -899,7 +899,7 @@ unsigned char *stream_read_line(stream_t *s, unsigned char *mem, int max,
// Reserve 1 byte of ptr for terminating \0.
int l = read_characters(s, &mem[read], max - read - 1, utf16);
if (l < 0 || memchr(&mem[read], '\0', l)) {
- MP_VERBOSE(s, "error reading line\n");
+ MP_WARN(s, "error reading line\n");
s->eof = false;
return NULL;
}