[GHC] #10303: Make it easier to print stack traces when debugging GHC itself

[GHC]

#10303: Make it easier to print stack traces when debugging GHC itself
-------------------------------------+-------------------------------------
        Reporter:  goldfire          |                   Owner:  goldfire
            Type:  task              |                  Status:  new
        Priority:  normal            |               Milestone:
       Component:  Compiler          |                 Version:  7.10.1
      Resolution:                    |                Keywords:
Operating System:  Unknown/Multiple  |            Architecture:
 Type of failure:  None/Unknown      |  Unknown/Multiple
      Blocked By:                    |               Test Case:
 Related Tickets:                    |                Blocking:
                                     |  Differential Revisions:
-------------------------------------+-------------------------------------

Comment (by rwbarton):

 Replying to [ticket:10303 goldfire]:
 > * Is it worth adding a new mode in `build.mk` that enables profiling,
 `DEBUG`, and `-fprof-auto`, just to get good stack traces?

 Yes.

 (Maybe in the future we'll be able to use DWARF debugging information to
 get this information in a standard build, but let's not let that keep us
 from implementing this now.)

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10303#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler