mandoc: When the stdout stream gets broken, there is no point in reading

mandoc: When the stdout stream gets broken, there is no point in reading

[schwarze]

Log Message:
-----------
When the stdout stream gets broken, there is no point in reading 
any more input files, and it would be misleading to start a parser,
because that would show randomly truncated text.  
Instead, print an error message and exit the program.

Issue found by Leah Neukirchen <leah at vuxu dot org>, who was
surprised to see half a manpage when her /tmp/ overflew.

Modified Files:
--------------
    mandoc:
        main.c

Revision Data
-------------
Index: main.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/main.c,v
retrieving revision 1.301
retrieving revision 1.302
diff -Lmain.c -Lmain.c -u -p -r1.301 -r1.302
--- main.c
+++ main.c
@@ -484,6 +484,17 @@ main(int argc, char *argv[])
 				passthrough(resp->file, fd,
 				    conf.output.synopsisonly);
 
+			if (ferror(stdout)) {
+				if (tag_files != NULL) {
+					warn("%s", tag_files->ofn);
+					tag_unlink();
+					tag_files = NULL;
+				} else
+					warn("stdout");
+				rc = MANDOCLEVEL_SYSERR;
+				break;
+			}
+
 			if (argc > 1 && curp.outtype <= OUTT_UTF8) {
 				if (curp.outdata == NULL)
 					outdata_alloc(&curp);
--
 To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv