(    char * name /* new directory name */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This command sets the default directory to <i>name</i> on the host where <b><a href="./windsh.html#top">windsh</a></b> isrunning. <p>To change to a different directory, specify one of the following: <ul><li>  An entire path name.  In Windows, the directory path must be prefixed with adrive name and colon.</li><li>   A directory name starting with any of the following; note that for Windowshosts, subdirectories can be separated with either aslash ( / ) or backslash ( \ ):<pre>\ibe    UNIX:    ~    /    ..    .    Windows:   \    /    ..    . </pre><ul><li>   A directory name to be appended to the current default directory.  </ul><p><p></blockquote><h4>EXAMPLE </h4><blockquote><p>On a UNIX host, the following changes the directoryto <b>~leslie/target/config</b>: <pre>    -&gt; cd "~leslie/target/config"</pre>On a Windows host, the following lines are equivalent and change the directory to <b>c:\leslie\target\config:</b> <pre>    -&gt; cd "c:\\leslie\\target\\config"    -&gt; cd "c:/leslie/target/config"</pre>Notice that the rules for C strings require that backslashes be doubled.<p></blockquote><h4>RETURNS </h4><blockquote><p>OK or ERROR. <p></blockquote><h4>SEE ALSO </h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>, <b><i><a href="./windsh.html#pwd">pwd</a></i>(&nbsp;)</b>,<i>Tornado User's Guide: Shell</i></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b><hr><a name="checkStack"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>checkStack</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>checkStack</i>(&nbsp;)</strong> - print a summary of each task's stack usage (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void checkStack    (    int taskNameOrId /* task name or task ID; 0 = summarize all */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This command displays a summary of stack usage for a specified task,or for all tasks if no argument is given.  The summary includes the totalstack size (SIZE), the current number of stack bytes used (CUR), themaximum number of stack bytes used (HIGH), and the number of bytes neverused at the top of the stack (MARGIN = SIZE - HIGH).For example:<pre>    -&gt; checkStack t28        NAME         ENTRY      TID    SIZE   CUR  HIGH  MARGIN    ------------ ------------ -------- ----- ----- ----- ------    t28          _foo         23e1c78   9208   832  3632   5576</pre>The maximum stack usage is determined by scanning down from the top of thestack for the first byte whose value is not 0xee.  In VxWorks, when a taskis spawned, all bytes of a task's stack are initialized to 0xee.<p></blockquote><h4>DEFICIENCIES</h4><blockquote><p>It is possible for a task to write beyond the end of its stack, butnot write into the last part of its stack.  This will not be detectedby <b><i><a href="./windsh.html#checkStack">checkStack</a></i>(&nbsp;)</b>.<p></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <i>Tornado User's Guide: Shell</i><hr><a name="classShow"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>classShow</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>classShow</i>(&nbsp;)</strong> - show information about a class of objects (*) (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void classShow    (    int classID    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>VxWorks kernel objects, such as semaphores, message queues, and so on, areorganized into distinct classes.  All objects of each class are anchoredin a class ID stored as a global variable.  Given any such class ID,<b><i><a href="./windsh.html#classShow">classShow</a></i>(&nbsp;)</b> displays overall information about the class, including themaximum object size, and the number of objects allocated, deallocated,initialized, and terminated in that class.  Because all the class IDglobals are recorded using a consistent naming convention, you can obtaina list of the class IDs available at any time with the following:<pre>    -&gt; lkup "ClassId"</pre>There is no target-resident version of <b><i><a href="./windsh.html#classShow">classShow</a></i>(&nbsp;)</b>.<p></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <i>Tornado User's Guide: Shell</i><hr><a name="cplusCtors"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>cplusCtors</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>cplusCtors</i>(&nbsp;)</strong> - call static constructors (C++) (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void cplusCtors    (    const char * moduleName /* name of loaded module */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This function is used to call static constructors under the manualstrategy (see <b><i><a href="./windsh.html#cplusXtorSet">cplusXtorSet</a></i>(&nbsp;)</b>).  <i>moduleName</i> is the name of anobject module that was "munched" before loading.  If <i>moduleName</i> is 0,then all static constructors, in all modules loaded by the target serverloader, are called.<p></blockquote><h4>EXAMPLES</h4><blockquote><p>The following example shows how to initialize the static objects inmodules called <b>applx.out</b> and <b>apply.out</b>.<p><pre>    -&gt; cplusCtors "applx.out"    value = 0 = 0x0    -&gt; cplusCtors "apply.out"    value = 0 = 0x0</pre>The following example shows how to initialize all the static objects that arecurrently loaded, with a single invocation of <b><i><a href="./windsh.html#cplusCtors">cplusCtors</a></i>(&nbsp;)</b>:<p><pre>    -&gt; cplusCtors    value = 0 = 0x0</pre></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <b><i><a href="./windsh.html#cplusXtorSet">cplusXtorSet</a></i>(&nbsp;)</b>,  <i>Tornado User's Guide: Shell</i><hr><a name="cplusDtors"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>cplusDtors</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>cplusDtors</i>(&nbsp;)</strong> - call static destructors (C++) (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void cplusDtors    (    const char * moduleName /* name of loaded module */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This function is used to call static destructors under the manualstrategy (see <b><i><a href="./windsh.html#cplusXtorSet">cplusXtorSet</a></i>(&nbsp;)</b>).  <i>moduleName</i> is the name of anobject module that was "munched" before loading.  If <i>moduleName</i> is 0,then all static destructors, in all modules loaded by the target serverloader, are called.<p></blockquote><h4>EXAMPLES</h4><blockquote><p>The following example shows how to destroy the static objects inmodules called <b>applx.out</b> and <b>apply.out</b>:<p><pre>    -&gt; cplusDtors "applx.out"    value = 0 = 0x0    -&gt; cplusDtors "apply.out"    value = 0 = 0x0</pre>The following example shows how to destroy all the static objects that arecurrently loaded, with a single invocation of cplusDtors:<p><pre>    -&gt; cplusDtors    value = 0 = 0x0</pre></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <b><i><a href="./windsh.html#cplusXtorSet">cplusXtorSet</a></i>(&nbsp;)</b>,  <i>Tornado User's Guide: Shell</i><hr><a name="cplusStratShow"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>cplusStratShow</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>cplusStratShow</i>(&nbsp;)</strong> - show C++ static constructors calling strategy (*) (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void cplusStratShow (void)</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This command shows the current C++ static constructor calling strategy.There are two static constructor calling strategies: <i>automatic</i>and <i>manual</i>.<p><pre>    -&gt; cplusStratShow    C++ ctors/dtors strategy set to MANUAL    value = 0 = 0x0</pre></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <b><i>cplusXtorsSet</i>(&nbsp;)</b>,  <i>Tornado User's Guide: Shell</i><hr><a name="cplusXtorSet"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>cplusXtorSet</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>cplusXtorSet</i>(&nbsp;)</strong> - change C++ static constructor calling strategy (C++) (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>void cplusXtorSet    (    int strategy /* constructor calling strategy */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This command sets the C++ static constructor calling strategyto <i>strategy</i>.  The default strategy is 0.<p>There are two static constructor calling strategies: <i>automatic</i>and <i>manual</i> represented by the following numeric codes:<table><tr valign=top><th align=left>Strategy   </th><th align=left> Code</tr><tr><td colspan="2"><hr></tr><tr valign=top><td align=left>manual     </td><td align=left> 0</tr><tr valign=top><td align=left>automatic  </td><td align=left> 1</tr><tr valign=top><td align=left></tr></tr></table>Under the manual strategy, a module's static constructors anddestructors are called by <b><i><a href="./windsh.html#cplusCtors">cplusCtors</a></i>(&nbsp;)</b> and <b><i><a href="./windsh.html#cplusDtors">cplusDtors</a></i>(&nbsp;)</b>, which arethemselves invoked manually.<p>Under the automatic strategy, a module's static constructors arecalled as a side-effect of loading the module using the target serverloader.  A module's static destructors are called as a side-effect ofunloading the module.<p></blockquote><h4>RETURNS</h4><blockquote><p>N/A<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./windsh.html#top">windsh</a></b>,  <b><i><a href="./windsh.html#cplusStratShow">cplusStratShow</a></i>(&nbsp;)</b>.<b><i><a href="./windsh.html#cplusCtors">cplusCtors</a></i>(&nbsp;)</b>,  <b><i><a href="./windsh.html#cplusDtors">cplusDtors</a></i>(&nbsp;)</b>,  <i>Tornado User's Guide: Shell</i><hr><a name="cret"></a><p align=right><a href="rtnIndex.html"><i>Tornado Tools :  Routines</i></a></p></blockquote><h1><i>cret</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  <p><strong><i>cret</i>(&nbsp;)</strong> - continue until the current subroutine returns (WindSh)</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>STATUS cret    (    int task /* task to continue, 0 = default */    )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This routine places a breakpoint at the return address of the currentsubroutine of a specified task, then continues execution of that task.<p>To execute enter: