wtx.html

vxworks相关论文

</blockquote><h1>WTX_CONSOLE_CREATE</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WTX_CONSOLE_CREATE</strong> - WTX create a virtual target console (UNIX only)</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WTX_MSG_CONSOLE_DESC
OUTPUT: WTX_MSG_CONSOLE_DESC
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request creates a console tty on a UNIX host that can be connected 
to target tasks via a virtual I/O channel.  
<p>
The input message is:
<p>
<pre>
typedef struct wtx_msg_console_desc	/* WTX Virtual console desc. */
    {
    WTX_CORE		wtxCore;	/* WTX message core          */

    WTX_CONSOLE_DESC	wtxConsDesc;	/* Console descriptor        */
    } WTX_MSG_CONSOLE_DESC;</pre>

<p>
where <b>WTX_CONSOLE_DESC</b> is defined as follows:
<p>
<pre>
typedef struct wtx_console_desc 	/* WTX Virtual console desc. */
    {
    INT32		fdIn;		/* Stdin for redirection     */
    INT32		fdOut;		/* Stdout for redirection    */
    INT32		pid;		/* Process identifier        */
    char *		name;		/* Console name              */
    char *		display;	/* Display name eg: host:0   */
    void *		pReserved;	/* Reserved                  */
    } WTX_CONSOLE_DESC;</pre>

<p>
Only the <b>name</b> field needs to be specified; all the other
fields are set to NULL.  The name passed in <b>wtxConsDesc.name</b> is used as
a title for the console window.  The name may be of arbitrary length and
content, including blank space.  If <b>wtxConsDesc.name</b> is NULL, the
console window is assigned an ASCII name of the form "target console <i>n</i>"
where <i>n</i> is  an integer which increments as new consoles are created.
The <b>wtxConsDesc.display</b> field can be used to specify the display host
(for example, hostname:0) when running in a X-Window environment.  If
<b>wtxConsDesc.display</b> is NULL, the display is the host where the target
server is running. The number of buffered lines (default 88) can be changed
by setting the environment variable <b>WTX_CONSOLE_LINES</b> to the number of
desired buffered lines. Set this variable before launching the target server.
<p>
This request also adds the console file descriptor(s) to the target server 
internal-file-descriptor list for use with virtual I/O redirection.
<p>
A virtual I/O console is destroyed using <b><a href="./wtx.html#WTX_CONSOLE_KILL">WTX_CONSOLE_KILL</a></b>.
<p>
</blockquote><h4>UNIX HOSTS </h4><blockquote><p>
On UNIX-based hosts, the virtual I/O console is an xterm process which 
is displayed on the host specified by <b>WTX_CONSOLE_DESC</b>.display'.
<p>
</blockquote><h4>WINDOWS HOSTS</h4><blockquote><p>
This request is not implemented on Windows.  Windows allows only one virtual
console and it must be started on the target server command line with the
<b>-c</b> option.
<p>
</blockquote><h4>ASSOCIATED EVENTS</h4><blockquote><p>
<p>
This request has no associated events.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
The <b>errCode</b> field in <b>WTX_CORE</b> contains OK, or an ERROR code if 
unable to create a virtual target console.  If <b>errCode</b> 
is OK, <b>WTX_CONSOLE_DESC</b> contains the console information.
The <b><a href="../../vxworks/bsp/pid7t/pid7t.html#top" >pid</a></b> field contains the identifier of the virtual console, which is
<b><a href="../../vxworks/bsp/pid7t/pid7t.html#top" >pid</a></b> is the xterm console process id.
<p>
</blockquote><h4>ACTION LOCATION</h4><blockquote><p>
<p>
Target server only
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WTX_ERR_SVR_CANT_START_CONSOLE</b>
<dd>

Failed to start the virtual target console process.
<p>
<dt>
<b>WTX_ERR_SVR_NOT_ENOUGH_MEMORY</b>
<dd>

Not enough memory on the target server host to create a virtual console.
<p>
<dt>
<b>WTX_ERR_SVR_SERVICE_NOT_AVAILABLE</b>
<dd>

Console creation not available (Windows host only).
<p>
<dt>
TIMEOUT
<dd>
 WTX RPC timeout. 
</dl>

<p>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtx.html#WTX_CONSOLE_KILL">WTX_CONSOLE_KILL</a></b>

<hr>
<a name="WTX_CONSOLE_KILL"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Protocol :  Requests</i></a></p>

</blockquote><h1>WTX_CONSOLE_KILL</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WTX_CONSOLE_KILL</strong> - WTX kill a virtual target console (UNIX only)</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WTX_MSG_PARAM
OUTPUT: WTX_MSG_RESULT
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request kills a virtual I/O console specified by its identifier in
the <b>value</b> field of <b>WTX_MSG_PARAM</b>.  It also removes any file descriptor 
associated with the console process from the target server
internal-file-descriptor list.
<p>
<pre>
typedef struct wtx_msg_param		/* Simple request parameter */
    {
    WTX_CORE		wtxCore;	/* WTX message core         */

    WTX_VALUE		param;		/* Param value of call      */
    } WTX_MSG_PARAM;</pre>

<p>
The result of this request is returned in a <b>WTX_MSG_RESULT</b> message
but the <b>val</b> field is not used and is always NULL.
<p>
<pre>
typedef struct wtx_msg_result		/* Simple request result */
    {
    WTX_CORE		wtxCore;	/* WTX message core      */

    WTX_VALUE		val;		/* Result value of call  */
    } WTX_MSG_RESULT;</pre>

<p>
</blockquote><h4>WINDOWS HOSTS</h4><blockquote><p>
This request is not implemented on Windows.  If issued, it returns an
error, but does not attempt to kill an existing console.
<p>
</blockquote><h4>ASSOCIATED EVENTS</h4><blockquote><p>
<p>
This request has no associated events.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or an ERROR code if unable to kill the virtual console.
<p>
</blockquote><h4>ACTION LOCATION</h4><blockquote><p>
<p>
Target server only
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WTX_ERR_SVR_INVALID_CONSOLE</b>
<dd>

Invalid console.
<p>
<dt>
<b>WTX_ERR_SVR_INVALID_FILE_DESCRIPTOR</b>
<dd>

Invalid file descriptor.  This can happen if a <b><a href="./wtx.html#WTX_CLOSE">WTX_CLOSE</a></b> request was made 
on the file descriptor associated with the console.
<p>
<dt>
TIMEOUT
<dd>
 WTX RPC timeout. 
</dl>

<p>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtx.html#WTX_CONSOLE_CREATE">WTX_CONSOLE_CREATE</a></b>

<hr>
<a name="WTX_CONTEXT_CONT"></a>
<p align=right>
<a href="rtnIndex.html"><i>WTX Protocol :  Requests</i></a></p>

</blockquote><h1>WTX_CONTEXT_CONT</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>WTX_CONTEXT_CONT</strong> - WTX continue a context on the target</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>INPUT: WTX_MSG_CONTEXT
OUTPUT: WTX_MSG_RESULT
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This request continues execution of a context on the remote target.  The 
context to be resumed is specified by <b>contextId</b>.
<p>
<pre>
typedef struct wtx_msg_context		/* Context message  */
    {
    WTX_CORE		wtxCore;	/* WTX message core */

    WTX_CONTEXT_TYPE	contextType;	/* Type of context  */
    WTX_CONTEXT_ID_T	contextId;	/* Context ID       */
    } WTX_MSG_CONTEXT;</pre>

<p>
The result of this request is returned in a <b>WTX_MSG_RESULT</b> message
but the <b>val</b> field is not used and is always NULL.
<p>
<pre>
typedef struct wtx_msg_result		/* Simple request result */
    {
    WTX_CORE		wtxCore;	/* WTX message core      */

    WTX_VALUE		val;		/* Result value of call  */
    } WTX_MSG_RESULT;</pre>

<p>
Note that this request is used to resume a context stopped at a 
breakpoint.  It should not be used to resume a context suspended via
<b><a href="./wtx.html#WTX_CONTEXT_SUSPEND">WTX_CONTEXT_SUSPEND</a></b>.  A suspended or just-created context should be resumed 
with <b><a href="./wtx.html#WTX_CONTEXT_RESUME">WTX_CONTEXT_RESUME</a></b>.
<p>
</blockquote><h4>ASSOCIATED EVENTS</h4><blockquote><p>
<p>
After calling this request, the following events can be generated by 
the target system:
<dl>
<dt>
<b>TEXT_ACCESS</b>
<dd>

An instruction fetch occurred at the specified address (breakpoint).
<p>
<dt>
<b>DATA_ACCESS</b>
<dd>

A data access occurred at the specified address.
<p>
<dt>
EXCEPTION
<dd>

The task got an exception (for example: BUS ERROR, ZERO DIVIDE).
<p>
<dt>
<b>CONTEXT_EXIT</b>
<dd>
 The task exited via <b><i><a href="../../vxworks/ref/taskLib.html#exit" >exit</a></i>(&nbsp;)</b>. 
</dl>

<p>

</blockquote><h4>RETURNS</h4><blockquote><p>
The <b>errCode</b> field in <b>WTX_CORE</b> contains OK, or an ERROR code if 
unable to resume the context.
<p>
</blockquote><h4>ACTION LOCATION</h4><blockquote><p>
<p>
Target only
<p>
</blockquote><h4>ERRORS</h4><blockquote><p>
<p>
<dl>
<dt>
<b>WTX_ERR_AGENT_UNSUPPORTED_REQUEST</b>
<dd>

Context continue is not supported by the debug agent.
<p>
<dt>
<b>WTX_ERR_AGENT_INVALID_CONTEXT</b>
<dd>

Invalid target system context.
<p>
<dt>
<b>WTX_ERR_AGENT_NO_RT_PROC</b>
<dd>

Target operating system does not support context continue.
<p>
<dt>
<b>WTX_ERR_AGENT_AGENT_MODE_ERROR</b>
<dd>

Attempt to continue the system context while in task mode.
<p>
<dt>
<b>WTX_ERR_AGENT_COMMUNICATION_ERROR</b>
<dd>

Failure while communicating with the target.
<p>
<dt>
TIMEOUT
<dd>
 WTX RPC timeout. 
</dl>

<p>

</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./wtx.html#WTX_CONTEXT_CREATE">WTX_CONTEXT_CREATE</a></b>, <b><a href="./wtx.html#WTX_CONTEXT_SUSPEND">WTX