<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.Code, li.Code, div.Code
{mso-style-name:Code;
mso-style-link:"Code Char";
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Courier New";
color:#1F497D;}
span.CodeChar
{mso-style-name:"Code Char";
mso-style-link:Code;
font-family:"Courier New";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
.MsoPapDefault
{mso-style-type:export-only;
margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Good idea. I think it’d great if Jost (or someone else) felt able to update those wiki pages with the info in his email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Simon<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> ghc-devs [mailto:ghc-devs-bounces@haskell.org]
<b>On Behalf Of </b>Lennart Kolmodin<br>
<b>Sent:</b> 15 May 2015 11:31<br>
<b>To:</b> Jost Berthold<br>
<b>Cc:</b> ghc-devs@haskell.org<br>
<b>Subject:</b> Re: Debugging the RTS<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
Searching for online resources brought me to <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<a href="https://ghc.haskell.org/trac/ghc/wiki/Debugging">https://ghc.haskell.org/trac/ghc/wiki/Debugging</a> and<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<a href="https://ghc.haskell.org/trac/ghc/wiki/Debugging/RuntimeSystem">https://ghc.haskell.org/trac/ghc/wiki/Debugging/RuntimeSystem</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
This mail seems to be a more detailed description than available on the wiki. That page refers to GHC 6.12.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
Would it make sense to add some info to the <a href="https://ghc.haskell.org/trac/ghc/wiki/Debugging/RuntimeSystem">
RuntimeSystem</a> page?<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
2015-05-14 16:21 GMT+02:00 Jost Berthold <<a href="mailto:berthold@mathematik.uni-marburg.de" target="_blank">berthold@mathematik.uni-marburg.de</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
Hi Eric,<br>
<br>
definitely not bit-rotted - the #if DEBUG code is what you get when you compile with -debug.<br>
<br>
Short roadmap:<br>
<br>
In general, GHC is built in many "ways", the -debug way is one.<br>
Some ways (like -threaded, -eventlog, -debug) are RTS-only, others (like -prof) lead to different library code.<br>
<br>
Ways are defined in compiler/main/DynFlags.hs as a Haskell data structure.<br>
In _dynamic_flags_, the actual flag strings for the ghc invocation are defined (like -prof, -threaded), they will activate the respective _Way_.<br>
_wayTag_, in turn, defines short names used as a suffix for *.o and *.a files, for instance *.p_o for profiling, *.l_o for eventlog.<br>
A number of other functions in there customise behaviour depending on the ways. Note _wayOptc_ which sets some options for the C compiler, like -DTRACING for the -eventlog way. However, it does not define DEBUG for the debug way!<br>
<br>
In mk/<a href="http://ways.mk" target="_blank">ways.mk</a> you will find all the short names, and some more options are defined (WAY_*_HC_OPTS). These definitions are for the driver script, and pass on the right (long-name) options to the Haskell compiler to
activate what is inside DynFlags (like -prof for WAY_p_HC_OPTS).<br>
Here we find<br>
WAY_debug_HC_OPTS= -static -optc-DDEBUG -ticky -DTICKY_TICKY<br>
which is what you were looking for<br>
<br>
To build a GHC with debug-way RTS, you need to add GhcRtsWays += debug to your <a href="http://build.mk" target="_blank">
build.mk</a> (also see mk/<a href="http://config.mk" target="_blank">config.mk</a>{.in}, which gathers the default ways to build depending on platform and build configuration).<br>
I guess this might produce quite a number of new warnings and errors if you do it on a new platform...<br>
<br>
Once you have built this, you can compile with -debug and pass RTS options to get debug traces and activate sanity checks, like so:<br>
ghc -debug -myprogram.hs -o myprogramDebug<br>
./myprogramDebug +RTS -Ds -DS<br>
(-DS = sanity checks on, -Ds = scheduler tracing)<br>
The usage message (see /rts/RtsFlags.c) tells you more options you can use.<br>
<br>
Happy debugging!<br>
/ Jost<br>
<br>
<br>
On 05/14/2015 10:00 PM, <a href="mailto:ghc-devs-request@haskell.org" target="_blank">
ghc-devs-request@haskell.org</a> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
Date: Thu, 14 May 2015 18:36:04 +1000<br>
From: Erik de Castro Lopo <<a href="mailto:mle%2Bhs@mega-nerd.com" target="_blank">mle+hs@mega-nerd.com</a>><br>
To: <a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
Subject: Debugging the RTS<br>
Message-ID: <<a href="mailto:20150514183604.2476baaaacd6a85ef1430b37@mega-nerd.com" target="_blank">20150514183604.2476baaaacd6a85ef1430b37@mega-nerd.com</a>><br>
Content-Type: text/plain; charset=US-ASCII<br>
<br>
Hi all,<br>
<br>
I'm trying to debug a AArch64/Linux specific RTS issue and digging<br>
around in the rts C code, I see a large amount of code wrapped in<br>
"#if DEBUG" type statements, but no way to enable in either<br>
mk/<a href="http://build.mk" target="_blank">build.mk</a> or it seems in any of the other build related settings<br>
files in the mk/ directory.<br>
<br>
The only way I have found to enable this debug code that actually<br>
works is to enable this DEBUG code is to edit mk/<a href="http://ghc.mk" target="_blank">ghc.mk</a> as follows:<br>
<br>
-STANDARD_OPTS += -DCOMPILING_RTS<br>
+STANDARD_OPTS += -DCOMPILING_RTS -DDEBUG<br>
<br>
However, once I do that I get a bunch of C synatx errors.<br>
<br>
I am doing this wrong or has the DEBUG code bit rotted?<br>
<br>
Cheers,<br>
Erik<o:p></o:p></p>
</blockquote>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:6.0pt;margin-left:0cm">
<o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>