From ef006dcae6b07a8abb7fed847fd4a9e647109584 Mon Sep 17 00:00:00 2001
From: wm4 <wm4@nowhere>
Date: Sun, 19 Jan 2014 20:38:01 +0100
Subject: 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()).
---
 stream/stream.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'stream')

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;
         }
-- 
cgit v1.2.3