Tracing In Multi-Threaded Applications - HP A4500A - VMEbus Single Board Computer 744 Motherboard Programmer's Manual

15:53:38 <- ap_set_env() = 0
attr = AP_CNTX_NAME
val->len = 4
val->buf = (4/4)
52 01 00 04 R....
• The amount of data displayed is based on the value set for
ap_trace_max_udata. For example, if ap_trace_max_udata is set to
16, only the first 16 bytes are displayed as shown below:
val->sad.buf = (16/22)
06 69 5F 73 73 65 6C 06 69 5F 74 73 65 6C 07
48.i_ssel.i_tsel.H
The item "(16/22)" indicates that 16 of the 22 bytes of data output is
displayed. The following line contains the actual data in both
hexadecimal and ASCII representation.
Note that for some of the A/P calls such as ap_snd(), ap_rcv() and
ap_poll() the notation ">" is used to indicate input parameters and "<"
indicates output parameters. For example:
14:53:40 -> ap_poll()
> nfds = 1
> timeout = -1
> fds = Ox68FAC6A8
> fds[0].fd = 3
> fds[0].events = Ox4
< fds[0].revents = Ox4
14:53:40 <- ap_poll() = 1

Tracing in Multi-threaded Applications

A/P API traces in multi-threaded applications include thread-ids of the
executing threads as part of the trace output. This identifies a particular
part of the trace output as belonging to a particular thread. The format
of the trace output for multi-threaded applications is as follows:
>>> thread-id = 5 >>>
Wed Mar 5 15:26:30 1997 -> ap_open()
<<< thread-id = 5 <<<
>>> thread-id = 6 >>>
Wed Mar 5 15:26:30 1997 -> ap_open()
<<< thread-id = 6 <<<
>>> thread-id = 7 >>>
Wed Mar 5 15:26:30 1997 -> ap_open()
<<< thread-id = 7 <<<
>>> thread-id = 5 >>>
> pathname = /dev/osipi
> oflags = 0x0
<<< thread-id = 5 <<<
Chapter 5
Troubleshooting Your Application
Using A/P API Tracing
73