Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > bd5c3d824c3db63ffd9226c15941e6ad > files > 2235

mozart-1.4.0-1mdv2010.0.i586.rpm

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>4 The Oz Debugger: ozd</TITLE><LINK href="ozdoc.css" rel="stylesheet" type="text/css"></HEAD><BODY><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node7.html#chapter.linker">&lt;&lt; Prev</A></TD><TD><A href="index.html">- Up -</A></TD><TD><A href="node13.html#chapter.profiler">Next &gt;&gt;</A></TD></TR></TABLE><DIV id="chapter.debugger"><H1><A name="chapter.debugger">4 The Oz Debugger: <CODE>ozd</CODE></A></H1><P>The Oz debugger is extensively documented in <A href="../ozcar/index.html">``The Mozart Debugger''</A>. We describe it here merely in its incarnation as a command line application. Furthermore, we only document its options.</P><P>If you have created an Oz application which you normally start from the shell as follows: </P><BLOCKQUOTE class="code"><CODE>Foo&nbsp;</CODE><I>Args</I><CODE>&nbsp;...&nbsp;</CODE></BLOCKQUOTE><P> Then you can run it under control of the Oz debugger by using the following command instead: </P><BLOCKQUOTE class="code"><CODE>ozd&nbsp;Foo&nbsp;--&nbsp;</CODE><I>Args</I><CODE>&nbsp;...</CODE></BLOCKQUOTE><P> Any Oz application can be run in the debugger, but you only get the full benefit of the debugging interface when the code being executed was compiled with the <CODE>-g</CODE> option to include debugging information.</P><P>The double dash <CODE>--</CODE> separates the arguments intended for <CODE>ozd</CODE> from those intended for the application being run under the debugger. </P><DL><DT><CODE>--help</CODE>, <CODE>-h</CODE>, <CODE>-?</CODE></DT><DD><P>Display information on legal options, then exit</P></DD><DT><CODE>-g</CODE>, <CODE>--debugger</CODE>, <CODE>--mode=debugger</CODE></DT><DD><P>This option is the default: it starts the debugger. The other possibility is <CODE>-p</CODE> to start the profiler (see <A href="node13.html#chapter.profiler">Chapter&nbsp;5</A>).</P></DD><DT><CODE>-r</CODE>, <CODE>--remotedebugger</CODE>, <CODE>--mode=remotedebugger</CODE></DT><DD><P>In this mode of operation, a debugger client is started and connects to a debugger server. The <CODE>--ticket</CODE> option is required.</P></DD><DT><CODE>-p</CODE>, <CODE>--profiler</CODE>, <CODE>--mode=profiler</CODE></DT><DD><P>This is the other mode of operation: it starts the profiler instead (see <A href="node13.html#chapter.profiler">Chapter&nbsp;5</A>).</P></DD><DT><CODE>-E</CODE>, <CODE>--(no)useemacs</CODE></DT><DD><P>Starts a subordinate Emacs process. This will be used to display the source code currently being debugged. You will also be able to set breakpoints easily on source lines.</P></DD><DT><CODE>--emacs=</CODE><I>FILE</I></DT><DD><P>Specifies the Emacs binary to run for option <CODE>-E</CODE>. The default is $<A name="label9"></A><A name="label10"></A><CODE>OZEMACS</CODE> if set, else <CODE>emacs</CODE>.</P></DD><DT><CODE>--ticket=</CODE><I>TICKET</I></DT><DD><P>Specifies the ticket to use for option <CODE>-r</CODE> to connect to the server.</P></DD></DL><P></P></DIV><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node7.html#chapter.linker">&lt;&lt; Prev</A></TD><TD><A href="index.html">- Up -</A></TD><TD><A href="node13.html#chapter.profiler">Next &gt;&gt;</A></TD></TR></TABLE><HR><ADDRESS><A href="http://www.ps.uni-sb.de/~duchier/">Denys&nbsp;Duchier</A>, <A href="http://www.ps.uni-sb.de/~kornstae/">Leif&nbsp;Kornstaedt</A> and&nbsp;<A href="http://www.ps.uni-sb.de/~schulte/">Christian&nbsp;Schulte</A><BR><SPAN class="version">Version 1.4.0 (20090610)</SPAN></ADDRESS></BODY></HTML>