Subject: Restore LockLint to the state it was in before the analysis and rerun the analysis as necessary.

From: "Hutchins Rosalia" <[email-masked]>
Date: Tue, 20 Mar 2007 20:18:38 -0600

All functions that are targets of a particular function pointer must have the same side effects on locks (if any).
c to write a rule to create a .
1111 in default mode, and 0.
If the state needs to be saved and restored repeatedly, simply save the state again immediately after restoring it, or use the refresh subcommand.
assert assert has the following syntax:  assert side effect  mutex  acquired in  func . If the state needs to be saved and restored repeatedly, simply save the state again immediately after restoring it, or use the refresh subcommand. Miscellaneous problems related to analysis of the source code in relation to assertions and locks. Lists only those locks that may be inverted by calling one of the specified functions.
These annotations are useful in functions that initialize data without holding locks before starting up any additional threads.
The Sun Studio Fortran 95 compiler has implemented many of the new features introduced in this standard. Note - Add assertions liberally, and use the analysis phase to refine assertions and to make sure that new code does not violate the established locking conventions of the program.
You can avoid some other problems by using conditionally compiled code in the application. The saved state stack is a LIFO (Last-In-First-Out) stack. However, if LockLint is not told about this coverage relationship, it assumes that the locks are being used according to the usual conventions and generates error messages.