- For the GHC 7.10 release, one of the major features we planned to try and merge was DWARF debugging information. This is actually a small component of larger ongoing work, including adding stack traces to Haskell executables. While, unfortunately, not all the work can be merged, we talked with Peter, and made a plan: our hope is to get Phab:D169 merged, which lays all the groundwork, followed by DWARF debugging information in the code generators. This will allow tools like `gdb` or other extensible debuggers to analyze C-- IR accurately for compiled executables. Peter has written up a wiki page, available at SourceNotes, describing the design. We hope to land all the core infrastructure in Phab:D169 soon, followed by DWARF information for the Native Code Generator, all for 7.10.1
I'm currently working on some internal changes in GHCJS to prepare for GHC 7.10, support source maps [1] and make the optimizer more effective and reliable (smaller/faster code!). So this change, retaining more source code location information, would still be very useful, even if you don't manage to land the whole NCG/Cmm part (GHCJS only uses STG). luite [1] https://developer.chrome.com/devtools/docs/javascript-debugging#source-maps