Minor additions to ease debugging. The first one is there so we can easily
print things like patch info or summary if --debug was given.

The second one is of obvious use (the need for profiling to be enabled is a
bit unfortunate). In case you wonder: yes, getting a stack trace is
available in ghc-7.4.1.

2 patches for repository http://darcs.net/screened:

patch c6cc3ff63b73909cd9cc85a300ab9856b389c2b2
Author: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
Date:   Wed Feb 11 01:08:48 CET 2015
  * added debugDocLn to Darcs.Util.Printer

patch ef32279fc7834282117053f01712bc07459da75f
Author: Ben Franksen <benjamin.franksen@helmholtz-berlin.de>
Date:   Wed Feb 11 01:12:02 CET 2015
  * errorDoc now prints a stack trace (if profiling was enabled)

Attachments

• added-debugdocln-to-darcs_util_printer.dpatch
• patch-preview.txt
• unnamed

I see another 'errorDoc' function in src/Darcs/Util/Printer/Color.hs.
Does it also need to be modified?

I only looked at Darcs.Util.Bug and what it imports. Yes, assertDoc
could be adapted in the same way. I have a patch but I would like to
factor out the unsafe/GHC stuff. Then I thought shouldn't both errorDoc
functions rather be in Darcs.Util.Bug instead of the Printer modules?