| Previous | Contents |
In Section 2.6.1.4, the following line should immediately precede the Section 4.29.5 heading:
Symbols can include lowercase letters. Commands that manipulate symbols
(such as
DEFINE
,
SHOW SYMBOL
, and
UNDEFINE
) require such symbols to be within quotes.
4.29.6 ANALYZE
In the Parameters section, Chapter 3, the of the file specifcation description should be as follows:
Name of file that contains the dump you want to analyze. If no file specification is given with an ANALYZE/CRASH_DUMP command, the default is the highest version of SYS$SYSTEM:SYSDUMP.DMP . If this file does not exist, SDA prompts you for a file name. If any field of file specification is given, the remaining fields default to the highest version of SYSDUMP.DMP in your default directory.
The following should be added to the Parameters section:
Collection-file-name
Name of the file to be used by SDA that contains the file ID
translation data and/or unwind data.
4.29.7 Crash_Dump
In Chapter 3, in the Format section,
filespec
should be
[ filespec ]
(that is, the filespec parameter is now optional).
4.29.8 SDA Commands
In the the Introduction to Chapter 4, FLT should be removed and the following commands added:
COLLECT
SHOW EFI
SHOW VHPT
VALIDATE POOL
VALIDATE PROCESS
4.29.9 Copy Command
In Chapter 4, the following content should be appended to the COPY command description:
When a dump is being analyzed, it is useful to have data available that cannot be written to the dump file at the time of the system crash. This data includes the full file specification associated with a file identification, and, on OpenVMS I64, the unwind data for images activated in processes.
If the dump is being analyzed on the system where it was originally written, this data can be collected for use in the current SDA session using the COLLECT command. If the dump is being copied for analysis elsewhere, the COPY/COLLECT command can be used to collect the data and append it to the copy being written. If the COPY/COLLECT command is used after a COLLECT command, the data already collected is appended to the dump copy.
By default, a copy of the original dump, as written at the time of the system crash, will include collection. You can use COPY/NOCOLLECT to override this. Conversely, a copy of a dump previously copied by SDA without collection (COPY/NOCOLLECT) does not include collection. You can use COPY/COLLECT to override this. Copying a dump that already contains an appended collection always includes that collection.
For all file and unwind data to be collected successfully, all disks that were mounted at the time of the system crash should be remounted and accessible to the process running SDA. If SDA is invoked early on during startup to save the contents of the dump, for example, using CLUE$SITE_PROC (see Section 2.2.3), but disks are not mounted until a batch job is run, then the COPY/NOCOLLECT command should be used in the CLUE$SITE_PROC command procedure. Once all disks are mounted, a COPY/COLLECT can be used to save file and unwind data.
If the
COPY
and the
COLLECT
commands cannot be issued as a single step, a
COLLECT/SAVE
command writes the collection to a separate file that can be used later
with the dump file. A later
COPY
command combines the two files.
4.29.10 DUMP Command
In Chapter 4, the following changes should be made to the DUMP command description:
In Chapter 4, the following changes should be made to the EVALUATE command description:
In Chapter 4, the following text should be appended to the end of the description section:
On OpenVMS for Integrity servers, the MAP command can also provide additional data for addresses in system space. If the address is determined to be in a code section of an executive loaded image or a resident shareable image, and if the image file is accessible and was linked /TRACEBACK , then the traceback data is used to obtain and display module name and routine name information.
In Chapter 4, the following example should be added to the MAP command description:
11. SDA> EVALUATE 2F0/SYMBOL=PCB*
Hex = 00000000.000002F0 Decimal = 752 PCB$L_INITIAL_KTB
PCB$L_PCB
|
This example shows the use of the symbol filter. Only symbols whose
value is 2F0 and whose names begin with PCB are displayed.
4.29.13 SET CPU Command
In Chapter 4, the following lines should be appended to the list of SET PROCESS and SHOW PROCESS commands:
VALIDATE PROCESS/POOL process-name
VALIDATE PROCESS/POOL/ADDRESS=pcb-address
VALIDATE PROCESS/POOL/INDEX=nn
VALIDATE PROCESS/POOL/NEXT
4.29.14 SET PROCESS Command
In Chapter 4, the following lines should be appended to the list of SET PROCESS and SHOW PROCESS commands:
VALIDATE PROCESS/POOL process-name
VALIDATE PROCESS/POOL/ADDRESS=pcb-address
VALIDATE PROCESS/POOL/INDEX=nn
VALIDATE PROCESS/POOL/NEXT
VALIDATE PROCESS/POOL/SYSTEM
4.29.15 READ Command
In Chapter 4, the following text should be appended to the end of the description section:
In the description of the directory-spec parameter, SYS$LOADABLE_IMAGES and SYS$LIBRARY should be changed to SYS$LOADABLE_IMAGES , SYS$LIBRARY , and SYS$SYSTEM .
In Table 4-1, footnote 3, the following sentence should be removed:
These are found in
SYS$SYSTEM
, and are not automatically read in when you issue a
READ/EXEC
command.
4.29.16 SEARCH Command
The following changes should be made to the SEARCH command description in Chapter 4:
In Chapter 4, the following text should replace the description of the starting-address parameter:
On Alpha:
An expression representing the starting address of the procedure call frame to be displayed. If no value for starting-address is given, the default starting address is the contents of the frame pointer (FP) register of the SDA current process. For a process that uses pthreads, the following SDA command can be used to display the starting addresses for all pthreads:
SDA> pthread thread -o u |
On OpenVMS for Integrity servers:
An expression representing one of the following:
SDA> SHOW CALL_FRAME /EXCEPTION_FRAME=starting-address |
SDA> pthread thread -o u |
In Chapter 4, the following changes should be made to the SHOW CLUSTER command description:
In the Format section, "/CIRCUIT=pb-addr |" should be placed before "/CSID."
In the qualifier description for /ADDRESS, "/CSID=csid and /NODE=name" should be replaced with "/CIRCUIT=pb-addr, /CSID=csid, and /NODE=name".
In the qualifier descriptions for /CSID and /NODE, "/CIRCUIT=pb-addr," should be added after "/ADDRESS=n".
The following text should be appended to the Description:
If the qualifier /CIRCUIT=pb-addr is specified, then the SHOW
CLUSTER command displays only the information from the specified path
block.
4.29.19 SHOW CRASH Command
The following changes should be made to the SHOW CRASH command description in Chapter 4:
The Format section should read, "SHOW CRASH [ /ALL | /CPU = n]".
In the Description section the following should be appended to the second-to-last paragraph:
Unless /ALL is specified, the registers (on Alpha) or exception frame contents (on I64) are omitted from the display for any CPUs with CPUEXIT or DBGCPUEXIT bugchecks.
In the Description section, the phrase "and additionally displays all CPU database addresses in system dumps" should be removed from the final paragraph.
The command in example 3 should be changed to the following:
SDA> SHOW CRASH /ALL |
In Chapter 4, the following changes should be made to the SHOW DUMP command description:
The Format section should be replaced with the following:
SHOW DUMP [ /ALL
| /BLOCK [ = m [ { : | ; } n ] ]
| /COLLECTION [ = { ALL | n } ]
| /COMPRESSION_MAP [ = m [ : n [ : p ] ] ]
| /ERROR_LOGS
| /FILE = { COLLECTION | DUMP }
| /HEADER
| /LMB [ = { ALL | n } ]
| /MEMORY_MAP
| /SUMMARY ]
|
In the Description section, the phrase "the memory map, and the file identification, and/or unwind data collection" should replace the phrase "and the memory map".
The following example should be appended to the SHOW DUMP command:
3. SDA> SHOW DUMP/COLLECTION File and unwind data collection ------------------------------- Collection start VBN: 0002155B Collection end VBN: 00022071 Collection block count: 00000B17 VBN Blocks> Contents -------- -------- ------------------------------ 0002155B 000000C1 Unwind data segment 00000001 of _$30$DKB200:[VMS$COMMON.SYSEXE]DCL.EXE;1 0002161C 00000001 Unwind data segment 00000001 of _$30$DKB200:[VMS$COMMON.SYSEXE]USB$UCM_SERVER.EXE;1 0002161D 0000000C Unwind data segment 00000008 of _$30$DKB200:[VMS$COMMON.SYSEXE]USB$UCM_SERVER.EXE;1 . . . 0002200F 0000001F Unwind data segment 00000007 of _$30$DKB200:[VMS$COMMON.SYSEXE]LATACP.EXE;1 0002202E 00000006 Unwind data segment 0000000B of _$30$DKB200:[VMS$COMMON.SYSEXE]LATACP.EXE;1 00022034 00000001 Unwind data segment 00000002 of _$30$DKB200:[BISHOP]CMEXEC_LOOP.EXE;1 00022035 00000001 File data for _$30$DKA0: 00022036 0000003B File data for _$30$DKB200: 00022071 00000001 Disk data |
This example of the SHOW DUMP/COLLECTION command shows the contents of
the file identification and/or unwind data collection appended to a
system dump when it was copied with the SDA command COPY/COLLECT. Note
that unwind data segments are found only in system dumps from OpenVMS
I64 systems.
4.29.21 SHOW PROCESS Command
In Chapter4, the following changes should be made to the SHOW PROCESS command description:
In the Format section:
In the description of qualifier /ALL, "/STATISTICS" should be added to the line "/POOL/HEADER/RING_BUFFER".
The heading and the first paragraph in the description for the /POOL qualifier should read:
/POOL [ = { P0 | P1 | IMGACT | ALL (D) } ]
Displays the dynamic storage pool in the process’s P0 (process) region and/or the P1 (control) region and/or the image activator’s reserved pages, or optionally, a range of addresses. The default action is to display all dynamic storage pools.
The following should replace the description for the /UNWIND_TABLE qualifier:
/UNWIND_TABLE [ = { ALL | name } ] (I64 only)
If specified without a keyword, displays the master unwind table for the process. SHOW PROCESS/UNWIND=ALL displays the details of every process unwind descriptor. SHOW PROCESS/UNWIND=name displays the details of every unwind descriptor for the named image(s) (wildcards allowed). To look at unwind data for a specific PC in process space, use SHOW UNWIND address.
If some or all unwind data for an image was not included in the system dump (for example, it was not in the working set of the process at the time of the system crash), a SHOW PROCESS/UNWIND command may fail with a %SDA-W-NOREAD error because the unwind data is inaccessible. Collecting unwind data (see Commands COLLECT and COPY/COLLECT) will not correct this, as the collected unwind data is only used by SHOW UNWIND address and SHOW CALL.
The second bullet under "For I64" should read as follows:
Special purpose registers (PC, PSR, ISR). Note that the PC is the combination of the IP and the slot number from the PSR.
4.29.22 SHOW RESOURCES Command
The following changes should be made to the SHOW RESOURCES command
description in Chapter 4:
The following keywords should be added to the /STATUS qualifier:
| Keyword | Meaning |
|---|---|
| RM_FORCE | Forced tree move |
| RM_FREEZE | Freeze resource tree on this node |
| RM_INTEREST | Remaster due to master having no interest |
| XVAL_VALID | Last value block was long block |
The following changes should be made to the SHOW SPINLOCKS command description in Chapter 4:
The Format section should read as follows:
SHOW SPINLOCKS {[name]|/ADDRESS = expression|/INDEX = expression }
[/OWNED|/DYNAMIC|/STATIC
|/CACHED_PCB|/MAILBOX|/PCB|/PORT|/PSHARED]
[{/BRIEF|/COUNTS|/FULL}]
|
In the description of the name parameter, the phrase "PCB, or cached PCB" should be changed to "PCB, cached PCB, or process-shared."
In the description of the /ADDRESS qualifier, the phrase "PCB, or cached PCB" should be changed to "PCB, cached PCB, or process-shared."
In the description of the /DYNAMIC qualifier, the phrase "PCB, or cached PCB" should be changed to "PCB, cached PCB, or process-shared." The following new qualifier should be added after the /PORT qualifier:
/PSHARED
Displays all process-shared (Pthreads) spinlocks.
In the third paragraph of the description section, the phrase "PCB and
cached PCB" should be changed to "PCB, cached PCB, and process-shared."
4.29.24 SHOW MEMORY Command
In Chapter 4,the following changes should be made to the SHOW MEMORY command description:
In the /SLOTS qualifier description, the word "partition" should be
"process."
4.29.25 SHOW GCT Command
The following changes should be made to the SHOW GCT command description in Chapter 4:
In the Format section, "[ CHILDREN ] |" should be "[ /CHILDREN ] |," and should be followed by "[ /FULL ] |".
In the Qualifiers section, the /FULL qualifier description should be added after /CHILDREN:
/FULL
When used with /CHILDREN, /OWNER=n, or /TYPE=type, the /FULL qualifier causes SDA to provide a detailed display of each node.
In the /OWNER and /TYPE descriptions, "Provides a detailed display of all nodes" should be replaced by "Displays all nodes".
In the /TYPE description, "CORE," "SOCKET," and "THREAD" should be
added (in alphabetical order) to the list of valid types.
4.29.26 SHOW CPU Command
The following should be appended to the SHOW CPU command description in Chapter 4:
The following text should be appended to the symbol-name parameter description:
Symbols that include lowercase letters must be enclosed in quotes.
4.29.28 SHOW UNWIND Command
The Format section should read as follows:
/IMAGE
SHOW UNWIND [address|/ALL|/IMAGE=name]
4.29.29 SHOW SWIS Command
The following changes should be made to the SHOW SWIS command description in Chapter 4:
SHOW SWIS [/RING_BUFFER [/CPU = (m, n,...)]] |
/CPU = ( m, n,...) |
The following qualifiers to the CLUE CONFIG command description in Chapter 5:
/CPU
Displays only the part of the system configuration that contains information about the system, memory and CPUs.
/ADAPTER
Displays only the part of the system configuration that contains information about the adapters and devices on the system.
The following sentence should be appended to the Description section:
If no qualifier is specified, the entire system configuration is
displayed.
4.29.31 CLUE REGISTER Command
In Chapter 5, the following changes apply to the CLUE REGISTER command description:
The Format section should read as follows:
CLUE REGISTER [/CPU [cpu-id|ALL]
| /PROCESS[/ADDRESS=n|INDEX=n
| /IDENTIFICATION=n|process-name|ALL]]
|
The parameters and qualifiers are the same as those used for the CLUE_CALL_FRAME command.
The following sentence should be appended to the Description section:
If neither /CPU nor /PROCESS is specified, the parameter
(CPU-id or process-name) is ignored and the registers
for the SDA current process are displayed.
4.29.32 I64 ISD_Labels Index Table
The following table replaces the I64 ISD_Labels Index Table in Chapter 10:
| Index | Name | Meaning |
|---|---|---|
| 0 | SDA_CIO$K_FIX | Fixup |
| 1 | SDA_CIO$K_PROMO_CODE | Promote (code) |
| 2 | SDA_CIO$K_PROMO_DATA | Promote (data) |
| 3 | SDA_CIO$K_INIT_CODE | Initialization (code) |
| 4 | SDA_CIO$K_INIT_DATA | Initialization (data) |
| 5 | SDA_CIO$K_CODE | Code |
| 6 | SDA_CIO$K_SHORT_RW | Short data (read/write) |
| 7 | SDA_CIO$K_SHORT_RO | Short data (read only) |
| 8 | SDA_CIO$K_RW | Data (read/write) |
| 9 | SDA_CIO$K_RO | Data (read only) |
| 10 | SDA_CIO$K_SHORT_DZ | Short data (demand zero) |
| 11 | SDA_CIO$K_SHORT_TDZ | Short data (trailing demand zero) |
| 12 | SDA_CIO$K_DZERO | Demand zero |
| 13 | SDA_CIO$K_TR_DZERO | Trailing demand zero |
| Previous | Next | Contents |