From e8f7543db0d83e06b227e12f33492109aea1403c Mon Sep 17 00:00:00 2001 From: Thomas Huth Date: Thu, 8 Jun 2017 14:23:29 +0200 Subject: paflof: Print stack warning to stderr, not stdout Now that stdout is routed through the TYPE Forth word, we should avoid using stdout in critical sections in the engine() function. So print the stack warning via stderr now instead. Signed-off-by: Thomas Huth Signed-off-by: Alexey Kardashevskiy --- slof/paflof.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'slof/paflof.c') diff --git a/slof/paflof.c b/slof/paflof.c index 5c4f4e1..50b4adf 100644 --- a/slof/paflof.c +++ b/slof/paflof.c @@ -90,7 +90,7 @@ long engine(int mode, long param_1, long param_2) } if ((char *)&ip < the_system_stack && !did_stackwarning) { - puts("ERROR: stack overflow in engine()!"); + fprintf(stderr, "\nERROR: stack overflow in engine()!\n"); did_stackwarning = 1; } -- cgit v1.1