HP 800 ACSE/Presentation and ROSE Interface Programmer's Guide - Page 74

unambiguously identifies the thread which has output these tracing

Page 74 highlights

Troubleshooting Your Application Using A/P API Tracing >>> thread-id = 6 >>> > pathname = /dev/osipi > oflags = 0x0 >> > pathname = /dev/osipi > oflags = 0x0 >> denotes that the lines following it have been output by the thread with the thread-id 5. Also, the line >> and

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109

74
Chapter 5
Troubleshooting Your Application
Using A/P API Tracing
>>> thread-id
= 6 >>>
>
pathname = /dev/osipi
>
oflags = 0x0
<<< thread-id
= 6 <<<
>>> thread-id
= 7 >>>
>
pathname = /dev/osipi
>
oflags = 0x0
<<< thread-id
= 7 <<<
The line
>>> thread-id = 5 >>>
denotes that the lines following it have
been output by the thread with the thread-id 5.
Also, the line
<<<
thread-id = 5 <<<
denotes the end of trace output from the thread with
thread-id 5.
So, every group of tracing lines is enclosed within lines of
the form
>>> thread-id = no >>>
and
<<< thread-id = no <<<
.
This
unambiguously identifies the thread which has output these tracing
lines.
The tracing output from various threads may be interleaved which
denotes that they are being scheduled in and out while they are
executing and doing tracing output.