dbglib.html

Vxworks API操作系统和驱动程序设计API。压缩的HTML文件

</blockquote><h4>RETURNS</h4><blockquote><p>
<p>
OK, or ERROR if the specified task does not exist.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <b><a href="./usrLib.html#tr">tr</a>(&nbsp;)</b>,  
<i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

<hr>
<a name="cret"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>cret(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cret(&nbsp;)</strong> - continue until the current subroutine returns</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 current
subroutine of a specified task, then continues execution of that task.
<p>
To execute, enter:
<pre>    -&gt; cret [task]
</pre>
If <i>task</i> is omitted or zero, the last task referenced is assumed.
<p>
When the breakpoint is hit, information about the task will be printed in
the same format as in single-stepping.  The breakpoint is automatically
removed when hit, or if the task hits another breakpoint first.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
<p>
OK, or ERROR if there is no such task or the breakpoint table is
full.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <b><a href="./dbgLib.html#so">so</a>(&nbsp;)</b>,  
<i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

<hr>
<a name="s"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>s(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>s(&nbsp;)</strong> - single-step a task</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS s
    (
    int     taskNameOrId,     /* task to step; 0 = use default */
    INSTR * addr,             /* address to step to; 0 = next instruction */
    INSTR * addr1             /* address for npc, 0 = next instruction */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine single-steps a task that is stopped at a breakpoint.  
<p>
To execute, enter:
<pre>    -&gt; s [task[,addr[,addr1]]]
</pre>
If <i>task</i> is omitted or zero, the last task referenced is assumed.
If <i>addr</i> is non-zero, then the program counter is changed to <i>addr</i>;
if <i>addr1</i> is non-zero, the next program counter is changed to <i>addr1</i>,
and the task is stepped.
<p>
</blockquote><h4>CAVEAT</h4><blockquote><p>
When a task is continued, <b><a href="./dbgLib.html#s">s</a>(&nbsp;)</b> does not distinguish between a suspended
task or a task suspended by the debugger.  Therefore, its use should be
restricted to only those tasks being debugged.
<p>
</blockquote><h4>NOTE</h4><blockquote><p>
The next program counter, <i>addr1</i>, is currently supported only by SPARC.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if the debugging package is not installed, the task
cannot be found, or the task is not suspended.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

<hr>
<a name="so"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>so(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>so(&nbsp;)</strong> - single-step, but step over a subroutine</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS so
    (
    int task                  /* task to step; 0 = use default */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine single-steps a task that is stopped at a breakpoint.
However, if the next instruction is a JSR or BSR, <b><a href="./dbgLib.html#so">so</a>(&nbsp;)</b> breaks at the
instruction following the subroutine call instead.
<p>
To execute, enter:
<pre>    -&gt; so [task]
</pre>
If <i>task</i> is omitted or zero, the last task referenced is assumed.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

<hr>
<a name="l"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>l(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>l(&nbsp;)</strong> - disassemble and display a specified number of instructions</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void l
    (
    INSTR * addr,             /* address of first instruction to */
                              /* disassemble if 0, continue from the last */
                              /* instruction disassembled on the last call */
                              /* to l */ 
    int     count             /* number of instruction to disassemble if */
                              /* 0, use the same as the last call to l */ 
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine disassembles a specified number of instructions and displays
them on standard output.  If the address of an instruction is entered in
the system symbol table, the symbol will be displayed as a label for that
instruction.  Also, addresses in the opcode field of instructions will be
displayed symbolically.
<p>
To execute, enter:
<pre>    -&gt; l [address [,count]]
</pre>
If <i>address</i> is omitted or zero, disassembly continues from the previous
address.  If <i>count</i> is omitted or zero, the last specified count is used
(initially 10).  As with all values entered via the shell, the address may
be typed symbolically.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

<hr>
<a name="tt"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>tt(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>tt(&nbsp;)</strong> - display a stack trace of a task</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS tt
    (
    int taskNameOrId          /* task name or task ID */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine displays a list of the nested routine calls that the specified
task is in.  Each routine call and its parameters are shown.
<p>
If <i>taskNameOrId</i> is not specified or zero, the last task referenced is
assumed.  The <b><a href="./dbgLib.html#tt">tt</a>(&nbsp;)</b> routine can only trace the stack of a task other than
itself.  For instance, when <b><a href="./dbgLib.html#tt">tt</a>(&nbsp;)</b> is called from the shell, it cannot trace
the shell's stack.
<p>
</blockquote><h4>EXAMPLE</h4><blockquote><p>
<pre>    -&gt; tt "logTask"
     3ab92 _vxTaskEntry   +10 : _logTask (0, 0, 0, 0, 0, 0, 0, 0, 0, 0)
      ee6e _logTask       +12 : _read (5, 3f8a10, 20)
      d460 _read          +10 : _iosRead (5, 3f8a10, 20)
      e234 _iosRead       +9c : _pipeRead (3fce1c, 3f8a10, 20)
     23978 _pipeRead      +24 : _semTake (3f8b78)
    value = 0 = 0x0
</pre>
This indicates that <b><a href="./logLib.html#logTask">logTask</a>(&nbsp;)</b> is currently in <b><a href="./semLib.html#semTake">semTake</a>(&nbsp;)</b> (with
one parameter) and was called by <b>pipeRead(&nbsp;)</b> (with three parameters),
which was called by <b>iosRead(&nbsp;)</b> (with three parameters), and so on.
<p>
</blockquote><h4>CAVEAT</h4><blockquote><p>
In order to do the trace, some assumptions are made.  In general, the
trace will work for all C language routines and for assembly language
routines that start with a LINK instruction.  Some C compilers require
specific flags to generate the LINK first.  Most VxWorks assembly language
routines include LINK instructions for this reason.  The trace facility
may produce inaccurate results or fail completely if the routine is
written in a language other than C, the routine's entry point is
non-standard, or the task's stack is corrupted.  Also, all parameters are
assumed to be 32-bit quantities, so structures passed as parameters will
be displayed as <i>long</i> integers.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
<p>
OK, or ERROR if the task does not exist.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dbgLib.html#top">dbgLib</a></b>, <i>VxWorks Programmer's Guide: Target Shell,  </i>
<b><a href="../../tornado/tools/windsh.html#top" >windsh</a></b>,  
<i>Tornado User's Guide: Shell</i>

</body>
</html>