HP-UX Reference (11i v2 03/08) - 2 System Calls (vol 5)

t
ttrace(2) ttrace(2)
these arguments, this address can be used to retrieve the full argument and environment
list.
Note: This request is not supported on PA-RISC versions of HP-UX.
Other Requests
All other requests, except non debug-related requests below, are targeted to a specific thread in the target
process. Also, all other requests require both the pid of the target process and an lwpid specifying a valid
thread in the target process. These requests are prefixed by
TT_LWP_ and are as follows:
TT_LWP_STOP
This request causes the thread identified by lwpid to stop executing. If the thread is already
stopped by the debugger,orby an event , an error is returned.
The addr , data and addr2 arguments must be zero.
TT_LWP_CONTINUE
This request causes the thread identified by lwpid to resume execution or, rather, to return to the
state it was in prior to being stopped by the debugger . If the thread had not previously been stopped
by the debugger, an error is returned.
If addr is not
TT_NOPC, that value is loaded in the program counter before execution is resumed.
Unexpected behavior will result if this value is not within the same function since only the PC, not
the context, is being modified.
If data is non-zero, it is expected to be a valid signal number and the thread will continue as if it
had received this signal.
The addr2 argument must be zero.
TT_LWP_SINGLE
This request causes the stopped thread identified by lwpid to resume execution for one machine
instruction. It causes a flag to be set so that an interrupt occurs upon the completion of one machine
instruction, and then executes the same steps as listed above for the TT_LWP_CONTINUE
request.
TT_LWP_TBRANCH
This request causes the stopped thread identified by lwpid to resume execution until a taken branch
instruction is executed. It causes a flag to be set so that an interrupt occurs upon completion of the
next taken branch instruction, and then executes the same steps as listed above for the
TT_LWP_CONTINUE request.
Note: This request is not supported on PA-RISC versions of HP-UX.
TT_LWP_GET_EVENT_MASK
This request is the same as TT_PROC_GET_EVENT_MASK
except for the thread identified by
lwpid.
TT_LWP_SET_EVENT_MASK
This request is the same as TT_PROC_SET_EVENT_MASK except for the thread identified by
lwpid.
TT_LWP_GET_SIGMASK
This request is the same as TT_PROC_GET_SIGMASK except for the thread identified by lwpid .
TT_LWP_SET_SIGMASK
This request is the same as TT_PROC_SET_SIGMASK except for the thread identified by lwpid .
TT_LWP_GET_STATE
This calls returns the state of the thread identified by lwpid . If the thread was not previously
stopped by the debugger or waiting to be continued after an event, an error is returned.
TT_LWP_SET_IBPT_REGS
TT_LWP_SET_DBPT_REGS
These requests write per-thread breakpoint values into breakpoint registers. data bytes from addr2
will be written to the instruction or data breakpoint register(s) named by addr. For Itanium-based,
addr must be an even number less than the value returned by TT_PROC_GET_NUM_IBPT_REGS
or TT_PROC_GET_NUM_DBPT_REGS respectively. data must be 16 bytes. The request will set a
value into the pair of instruction or data breakpoint registers addr and addr+1 . These values will
be enabled only when the specified thread is running. They are identical to
TT_PROC_SET_IBPT_REGS and TT_PROC_SET_DBPT_REGS respectively in other respects.
HP-UX 11i Version 2: August 2003 − 8 − Hewlett-Packard Company Section 2−−445