From e2998d720c6b6bf72c86201d816f256a8ba704e6 Mon Sep 17 00:00:00 2001 From: Simon Peyton Jones Date: Thu, 4 Jan 2018 16:12:39 +0000 Subject: Stop double-stacktrace in ASSERT failures We were getting the stack trace printed twice in assertion failures (e.g. see the Description of Trac #14552). This fixes it, by deleting code. (c.f. Trac #14635 which reports the same bug in documentation). --- compiler/utils/Outputable.hs | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'compiler/utils/Outputable.hs') diff --git a/compiler/utils/Outputable.hs b/compiler/utils/Outputable.hs index 3050fa1cf1..793b8fb139 100644 --- a/compiler/utils/Outputable.hs +++ b/compiler/utils/Outputable.hs @@ -1203,9 +1203,7 @@ warnPprTrace True file line msg x -- line number. Should typically be accessed with the ASSERT family of macros assertPprPanic :: HasCallStack => String -> Int -> SDoc -> a assertPprPanic _file _line msg - = pprPanic "ASSERT failed!" doc - where - doc = sep [ msg, callStackDoc ] + = pprPanic "ASSERT failed!" msg pprDebugAndThen :: DynFlags -> (String -> a) -> SDoc -> SDoc -> a pprDebugAndThen dflags cont heading pretty_msg -- cgit v1.2.1