Analyzing Program Performance With Sun WorkShop

Subcommand Summary

Table A-1 contains a summary of LockLint subcommands.

Table A-1 LockLint Subcommands


Subcommand	Effect
`analyze`	Tests the loaded files for lock inconsistencies; also validates against assertions
`assert`	Specifies what LockLint should expect to see regarding accesses and modifications to locks and variables
`declare`	Passes information to LockLint that it cannot deduce
`disallow`	Excludes the specified calling sequence in the analysis
`disallows`	Lists the calling sequences that are excluded from the analysis
`files`	Lists the source code files loaded via the `load` subcommand
`funcptrs`	Lists information about function pointers
`funcs`	Lists information about specific functions
`help`	Provides information about the specified keyword
`ignore`	Excludes the specified functions and variables from analysis
`load`	Specifies the `.ll` files to be loaded
`locks`	Lists information about locks
`members`	Lists members of the specified struct
`order`	Shows information about the order in which locks are acquired
`pointer calls`	Lists calls made through function pointers
`reallow`	Allows exceptions to the `disallow` subcommand
`reallows`	Lists the calling sequences reallowed through the `reallow` subcommand
`refresh`	Restores and then saves the latest saved state again
`restore`	Restores the latest saved state
`save`	Saves the current state on a stack
`saves`	Lists the states saved on the stack through the `save` subcommand
`start`	Starts a LockLint session
`sym`	Lists the fully qualified names of functions and variables associated with the specified name
`unassert`	Removes some assertions specified through the `assert` subcommand
`vars`	Lists information about variables

Many LockLint subcommands require you to specify names of locks, variables, pointers, and functions. In C, it is possible for names to be ambiguous. See "LockLint Naming Conventions" for details on specifying names to LockLint subcommands.

Table A-2 lists the exit status values of LockLint subcommands.

Table A-2 Exit Status Values of LockLint Subcommands


Value	Meaning
0	Normal
1	System error
2	User error, such as incorrect options or undefined name
3	Multiple errors
5	LockLint detected error: violation of an assertion, potential data race or deadlock may have been found, unprotected data references, and so on.
10	Licensing error