	» Error: configuration environment variable `variable-name` - unable to process
	» Error: configuration file variable `variable-name` - unable to process
	» Error: file `filename`, line `line-number` - configuration file format error
	» Error: memory allocation error
	» Error: programming error
	» Error: unable to determine current directory
	» Error: configuration error - STK_DB_HOME not set
	» Error: database configuration file error
	» Error: file `filename` - database file error
	» Error: rule configuration error
	» Error: Unrecognized option: `option-specifier`
	» Error: `option-argument` is specified with both `option-specifier1` and `option-specifier2` options - ambiguous
	» Error: `option-specifier1` `option-argument` conflicts with previous `option-specifier2` option(s)
	» Error: unable to parse option arguments
	» Error: no files specified to scan
	» Warning: multiple file types specified for `filename/extension/interpreter` in configuration
	» Warning: invalid `option-specifier` option: `option-argument` - skipping
	» Warning: `option-argument` - invalid line number specified for `option-specifier` option - skipping
	» Warning: file `filename` - unable to add to scan file list - skipping
	» Warning: file `filename` - unable to add to exclusion list - skipping
	» Warning: filename `filename` - unable to convert for file type identification
	» Warning: filename `filename` - unable to convert to absolute path name
	» Warning: `filename` is not a directory - skipping
	» Warning: directory `directory-name` - unable to access - skipping
	» Warning: directory `directory-name` - unable to perform find in - skipping
	» Warning: file `filename` has been excluded - skipping
	» Warning: file `filename` is excluded - skipping
	» Warning: file `filename` is not accessible - skipping
	» Warning: file `filename` has zero size - skipping
	» Warning: file `filename` is not a regular file - skipping
	» Warning: file `filename` could not be opened - skipping
	» Error: file `filename` - unable to open
	» Warning: file `filename` could not be read - skipping
	» Warning: file `filename` could not be rewound - skipping
	» Warning: file `filename` is executable - skipping
	» Warning: file `filename` is binary - skipping
	» Warning: file `filename` is binary or corrupt - skipping
	» Warning: file `filename` is of unknown type - skipping
	» Warning: file `filename` is of unknown type - generic scan can cause overreporting
	» Warning: file `filename`, line `line-number` - syntax error - attempting to recover
	» Warning: file `filename` - unable to recover from syntax error - skipping
	» FYI: file `filename` - recovered from syntax error - continuing
	» Warning: file `filename`, line `line-number` - illegal number - continuing
	» Warning: file `filename`, line `line-number` - excessive nesting of #if's - skipping
	» Warning: file `filename`, line `line-number` - missing continuation line - skipping
	» Warning: file `filename`, line `line-number` - illegal character `character` in #if
	» Warning: file `filename`, line `line-number` - error handling nesting - continuing
	» Warning: file `filename`, line `line-number` - #else without corresponding #if
	» Warning: file `filename`, line `line-number` - #endif without corresponding #if
	» Warning: file `filename`, line `line-number` - unexpected EOF within #if
	» Warning: file `filename`, line `line-number` - unexpected EOLN within quoted text
	» Warning: file `filename`, line `line-number` - unexpected EOF within quoted text
	» Warning: file `filename`, line `line-number` - unexpected EOF within C comment
	» Warning: file `filename`, line `line-number` - nested C comment
	» Warning: file `filename`, line `line-number` - unexpected EOF within braces {...}.
	» Warning: file `filename`, line `line-number` - unexpected ending brace
	» Your report is located in file `report-filename`
	» Use the following URL to access your report: file:`report-filename`

Error: configuration file variable variable-name - unable to process.: The file scanner could not correctly process the specified variable in the STK client configuration file (usually /etc/opt/STK/config/client). An error occurred when the file scanner attempted to convert the value of that variable between a wide character string and a multi-byte character string. This happens when the value contains one or more characters that are not part of the language codeset being used by the file scanner. First, ensure that the value specified for the variable is correct. Then check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Error: file filename, line line-number - configuration file format error.: The specified line in the STK client configuration file filename (usually /etc/opt/STK/config/client) is formatted incorrectly. Lines in this file, except for comments, take the form name=value, where only value can be left blank. Comment lines must begin with a pound sign (#) in the first column. Blank lines are also allowed. Edit this file to fix any formatting problems that occur on the specified line.

Error: configuration environment variable variable-name - unable to process.: The file scanner could not correctly process the specified environment variable. An error occurred when the file scanner attempted to convert the value of that variable between a wide character string and a multi-byte character string. This happens when the value contains one or more characters that are not part of the language codeset being used by the file scanner. First, ensure that the value specified for the variable is correct. If the variable was set in error, use unset variable-name (for the POSIX shell). Then check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Error: memory allocation error.: The file scanner was unable to allocate enough memory. This can happen if you are trying to scan a very large file or group of files. Try scanning any very large files separately, or reduce the number of files that you are scanning at one time. If you still get this error message, please contact your HP Support Representative or send email using the STK feedback form.

Error: programming error.: An internal bug was detected within the file scanner. Please contact your HP Support Representative or send email using the STK feedback form.

Error: unable to determine current directory.: The file scanner was unable to determine the current working directory, which it uses to convert relative file names to absolute file names. This message should have been immediately followed by another message explaining the cause of the failure. The most likely cause is a permissions problem. Ensure that your current directory, and all of its parent directories, are readable and searchable. If permissions are set correctly and you still get this error, please contact your HP Support Representative or use the STK feedback form.

Error: configuration error - STK_DB_HOME not set.: The STK_DB_HOME variable has not been set. The file scanner uses this variable to locate the database it uses to find transition problems in the files it is scanning. By default, this database is located in the directory /opt/STK/lib. If the database on your system has been moved to another directory, determine its new location and set the STK_DB_HOME variable in the STK client configuration file (usually /etc/opt/STK/config/client). Add a line of the form STK_DB_HOME=directory-name, where directory-name is the name of the directory containing the STK transition problem database. Ensure that only one line in the file starts with STK_DB_HOME=. The STK_DB_HOME variable can also be set with an environment variable of the same name, giving it the name of the directory containing the STK transition problem database as a value. If STK_DB_HOME is set in the STK client configuration file and in the environment, the environment setting takes precedence.

Error: database configuration file error.: The configuration file for the STK transition problem database contains incorrectly formatted or invalid data. Try re-installing the STK tools package or download a new version of the STK. If you still receive this message, please contact your HP Support Representative or send email using the STK feedback form.

Error: file filename - database file error.: The STK transition problem database file named in the message contains incorrectly formatted or invalid data. Try re-installing the STK tools package or download a new version of the STK. If you still receive this message, please contact your HP Support Representative or send email using the STK feedback form.

Error: rule configuration error.: The STK rule configuration file contains incorrectly formatted or invalid data. The file scanner uses the information in this file to determine the identifier type for each identifier that it finds when scanning a file. Try re-installing the STK tools package or download a new version of the STK. If you still receive this message, please contact your HP Support Representative or send email using the STK feedback form.

Error: Unrecognized option: option-specifier.: The specified file scanner option was not recognized. For valid options, see the scandetail(1) man page.

Error: option-argument is specified with both option-specifier1 and option-specifier2 options - ambiguous.: The option argument cannot be specified for both of the options. For example, the same symbol name cannot be specified as both defined, using the -D option, and undefined, using the -U option. Check the file scanner options that you are using and remove any of these types of ambiguities.

Error: option-specifier1 option-argument conflicts with previous option-specifier2 option(s).: Positive and negative logic cannot be used with the same option in a single command line. For example, the +C and -C options cannot both be used for any one run of the file scanner. Check the file scanner options that you are using and remove any of these ambiguities.

Error: unable to parse option arguments.: The file scanner could not process the options designated for that scan. An error occurred when the file scanner attempted to convert one of the option arguments between a wide character string and a multi-byte string. This happens when an argument contains one or more characters that are not part of the language codeset being used by the file scanner. First, ensure that the option arguments you are using are correct. Then check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used. If you are unable to resolve this problem, please contact your HP Support Representative or use the STK feedback form.

Error: no files specified to scan.: No files were specified for scanning. For information on using the file scanner, refer to the scandetail(1) man page.

Warning: multiple file types specified for filename/extension/interpreter in configuration.

More than one source file type is associated with the specified file name, extension, or interpreter. As a result, the file scanner may incorrectly identify the file type for one or more of the files that it scans. The file type determines which set of rules the file scanner uses to detect impacts in the file. Incorrect impacts may be reported for files that have been scanned with an incorrectly determined file type.

To determine the source file type, the file scanner uses a set of variables. Each variable is associated with a particular type of source file and method of determining the source file type (by file name, by extension, or by interpreter). For example, the CXX_EXTENSIONS variable lists the file name extensions that identify C++ source files (CXX_EXTENSIONS=C, cxx, cc, cpp, H, hxx, hh, hpp). The list of variables and their descriptions can be found in the STK client configuration file (usually /etc/opt/STK/config/client).

Ensure that the value specified in the message is listed in only one of the file name lists, one of the extension lists, and/or one of the interpreter lists. For example, the .f extension can be listed as either a fixed-format FORTRAN extension or as a free-format FORTRAN extension, but not both. Resolve any conflicts that you find.

Each of the individual variables used for determining file types can also be set using an environment variable of the same name. The environment variable setting takes precedence. You may also need to check these settings for conflicts.

Warning: invalid option-specifier option: option-argument - skipping.: An unrecognized value was specified for the option. That value is ignored and has no effect on the file scanner output. Ensure that you have specified recognized values for the option listed in the message. For a list of valid arguments for an option, refer to the scandetail(1) man page.

Warning: option-argument - invalid line number specified for option-specifier option - skipping.: An invalid line number was specified as an argument to the option. Line numbers must be greater than or equal to 1. The invalid line number is ignored and has no effect on the file scanner output.

Warning: file filename - unable to add to scan file list - skipping.: The file scanner could not add the specified file to the list of files that it should scan because it could not determine the file's absolute path. The specified file is not scanned. An error occurred when the file scanner attempted to convert either the specified file name or the path name for your current working directory (which is used to determine a file's absolute path) between a wide character string and a multi-byte string. This happens when the file name or path name contain one or more characters that are not part of the language codeset being used by the file scanner. Check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Warning: file filename - unable to add to exclusion list - skipping.: Depending on which option the specified file name was used with (-F or -L), the file scanner was either unable to add that file to the list of files that it should not scan, or was unable to add any lines within that file to the list of lines that it should not scan. The specified file, or lines from that file, may be scanned. The file scanner was unable to determine the specified file's absolute path. An error occurred when the file scanner attempted to convert either the specified file name or the path name for your current working directory (which is used to determine a file's absolute path) between a wide character string and a multi-byte string. This happens when the file name or path name contain one or more characters that are not part of the language codeset being used by the file scanner. Check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Warning: filename filename - unable to convert for file type identification.: The file scanner could not use the specified file's name or extension to determine the type of source contained in the file. It also could not determine whether the file was to be excluded based on its name or extension. The file scanner assumes that the file is not to be excluded and attempts to determine the file's source type using other means. If the file was not to be excluded and the file scanner is able to determine the file's type using other means, there should be no effect on your file scanner output. If the file scanner is unable to determine the file's type, another message is displayed to inform you that the file's source type is unknown and to inform you of the action being taken by the file scanner with regard to the specified file.
An error occurred when the file scanner attempted to convert the specified file name, or a portion of the specified file name, between a wide character string and a multi-byte character string. This probably happened because the file scanner was unable to allocate the small amount of memory needed to perform the conversion. It can also happen when the file name contains one or more characters that are not part of the language codeset being used by the file scanners. Check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Warning: filename filename - unable to convert to absolute path name.: The file scanner could not determine the absolute path for the specified file name. It normally uses the path name to tell you to access your file scanner report output. Instead, it uses the specified file name. This has no effect on your file scanner output. An error occurred when the file scanner attempted to convert either the specified file name or the path name for your current working directory (which is used to determine a file's absolute path) between a multi-byte character string and a wide character string. This happens when the file name or path name contains one or more characters that are not part of the language codeset being used by the file scanner. Then check that the file scanner is using the correct language codeset, as specified by the LANG environment variable. If LANG is not set, C is used.

Warning: filename is not a directory - skipping.: The file name was specified as an argument to the -r option, which is used to list the names of directories that the file scanner should recurse to find files for scanning. The specified file name is not the name of a directory, so the file scanner skips it. Ensure that any arguments to the -r option are specified correctly.

Warning: directory directory-name - unable to access - skipping.

The directory name was specified as an argument to the -r option, which is used to list the names of directories that the file scanner should recurse to find files for scanning. The file scanner was unable to access the specified directory, so its files were not scanned.

This message should have been immediately followed by another message explaining the cause of the failure. The most likely cause is that the specified directory does not exist. Ensure that the directory name is specified correctly.

Another likely cause of a directory's being inaccessible is a permissions problem. Ensure that the specified directory and all of its parent directories are readable and searchable.

An error may also have occurred when processing symbolic links in the specified directory's name. If this is the case, use a directory name that contains fewer symbolic links.

Warning: directory directory-name - unable to perform find in - skipping.: The directory name was specified as an argument to the -r option, which is used to list the names of directories that the file scanner should recurse to find files for scanning. The file scanner was unable to access the specified directory, so its files were not scanned.
The file scanner may not be able to recurse the specified directory for several possible reasons. This message should have been immediately followed by another message explaining the reason. If you need help resolving this problem, please contact your HP Support Representative or use the STK feedback form.

Warning: file filename has been excluded - skipping.: The specified file is not being scanned because it was also excluded using the -F option.

Warning: file filename is excluded - skipping.: The specified file is not being scanned because it was excluded based on its file name or extension.
The file scanner uses two variables, EXCLUDE_FIRSTNAMES and EXCLUDE_EXTENSIONS, to exclude groups of files from being scanned. For example, the EXCLUDE_EXTENSIONS variable could be set to exclude all object (.o) files. These two variables can be set in the STK client configuration file (usually /etc/opt/STK/config/client), or with environment variables of the same name. The environment variable settings override settings in the configuration file.

Warning: file filename is not accessible - skipping.

The file scanner could not access the specified file. This message should have been immediately followed by another message explaining the reason. The most likely reason for this failure is that the specified file does not exist. Ensure that the file was specified correctly.

Another likely reason is a permissions problem. Ensure that the specified file and all of the directories in its path are readable and searchable.

An error may also have occurred when processing symbolic links in the specified file's path. Replace the specified file name with one that contains fewer symbolic links.

Warning: file filename has zero size - skipping.: The specified file is empty and cannot be scanned.

Warning: file filename is not a regular file - skipping.: The specified file is not a regular file. For instance, it may be a directory or a device file. This file was either one that was to be scanned or it was specified with the -f option as containing a list of files that should be scanned. In either case, this file is not processed by the file scanner.

Warning: file filename could not be opened - skipping.: The file scanner could not open the specified file. This message should have been immediately followed by another message explaining the reason for the failure. If the specified file is one that was to be scanned or is a file that was specified with the -f option, the most likely reason for this failure is a permissions problem. Ensure that the specified file is readable and that all of the directories in the file's path are searchable. If permissions are correct or if the file is not one that you recognize as being yours, please contact your HP Support Representative or use the STK feedback form.

Error: file filename - unable to open.

The file scanner could not open the specified file. This message should have been immediately followed by another message explaining the reason for the failure.

The specified file might be a report output file that the file scanners were attempting to create. If so, it should have _detail or _summary at the end of its base name. If this is the case, the most likely reason for this failure is a permissions problem. Ensure that your current directory is writable and that all of the directories in the file's path are searchable. If you are unable to resolve this problem, please contact your HP Support Representative or send email using the STK feedback form.

The specified file might also be one of the file scanner's configuration or database files. If this is the case, please contact your HP Support Representative or send email using the STK feedback form.

Warning: file filename could not be read - skipping.: The file scanner could not read the specified file. This file is either one that was to be scanned, or it is one that was specified with the -f option as containing a list of files that should be scanned. In either case, this file is not processed by the file scanner. If the file was specified with the -f option, then the files listed in it are not scanned.
This error could occur for several possible reasons. This message should have been immediately followed by another message explaining the reason for the failure.

Warning: file filename could not be rewound - skipping.: The specified file is not being scanned because the file scanner could not rewind the file back to its beginning after either reading the file's magic number to find out if it is an executable, reading the first line in the file to find an interpreter to use in determining the type of the file, or attempting to determine if the file is binary.
This error could occur for several possible reasons. This message should have been immediately followed by another message explaining the reason for the failure.

Warning: file filename is executable - skipping.: The specified file is not being scanned because it is an executable, as determined using the file's magic number.

Warning: file filename is binary - skipping.: The specified file is not scanned because it is binary.

Warning: file filename is binary or corrupt - skipping.: The specified file is not scanned because it is binary or has been corrupted.

Warning: file filename is of unknown type - skipping.: The file scanner could not determine the type of the specified file, and does not scan the file because the -u option was used. See scanning unrecognized file types for more information.

Warning: file filename is of unknown type - generic scan can cause overreporting.: The file scanner could not determine the type of source contained in the specified file. The file is scanned, but the file scanner can not ignore comments or determine appropriate types for the identifiers in the file. This causes the file scanner to overreport. See scanning unrecognized file types for more information.
To make the file scanner avoid scanning files for which it cannot determine type, use the -u option. See the scandetail(1) man page.

Warning: file filename, line line-number - syntax error - attempting to recover.: The file scanner encountered a syntax error in the specified file when it was attempting to process symbols specified with the -D and/or -U options, and is attempting to recover. This message should be immediately followed by another message telling you whether the attempt was successful or not, and if not, what action was taken.

Warning: file filename - unable to recover from syntax error - skipping.: The file scanner encountered a syntax error in the specified file when it was attempting to process symbols that were specified using the -D and/or -U options. It could not recover from the error, so the specified file was not scanned.
Check the specified file and correct any syntax errors (the line number of the syntax error is listed in the message that preceded this message). If you cannot find the syntax error, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

FYI: file filename - recovered from syntax error - continuing.: The file scanner encountered a syntax error in the specified file when it was attempting to process symbols that were specified using the -D and/or -U options. It successfully recovered from the error and continued to scan the specified file. However, the file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
Check the specified file and correct any syntax errors (the line number of the syntax error is listed in the message that preceded this message). If you cannot find the syntax error, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - illegal number - continuing.: The file scanner detected an illegal hexadecimal number specification in the specified file while it was attempting to process symbols that were specified using the -D and/or -U options. However, the file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
Check the specified file and correct any illegal number specification (the line number of the error is listed in the message). If you cannot find the error, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - excessive nesting of #if's - skipping.: The specified file contains more levels of #if-style preprocessor directive nesting than the file scanner can handle when processing symbols specified with the -D and -U options. The specified file was not scanned. Scan the file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - missing continuation line - skipping.: The file scanner detected a missing continuation line while it was attempting to process symbols that were specified using the -D and/or -U options. The specified file was not scanned.
Check the specified file and correct the error (the line number of the error is listed in the message). If you cannot find the error, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - illegal character character in #if.: The file scanner detected an illegal character within a #if-style preprocessing directive while it was attempting to process symbols specified using the -D and/or -U options. That character was ignored.

Warning: file filename, line line-number - error handling nesting - continuing.: The specified file contains more levels of #if-style preprocessor directive nesting than the file scanner can handle when processing symbols specified with the -D and -U options. The file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
One possible cause of this error is that the file scanner does not process #elif preprocessor directives. If the specified file does not contain any #elif directives, check the file for any #if-style directive nesting errors. If you cannot find any such errors or if the file contains #elif directives, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - #else without corresponding #if.: The file scanner was unable to match an #else preprocessor directive to a corresponding #if directive while it was processing symbols specified with the -D and -U options. The file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
One possible cause of this error is that the file scanner does not process #elif preprocessor directives. If the specified file does not contain any #elif directives, check the file for any unmatched #else directives. If you cannot find any such errors or if the file contains #elif directives, scan the specified file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - #endif without corresponding #if.: The file scanner could not match an #endif preprocessor directive to a corresponding #if directive while it was processing symbols specified with the -D and -U options. The file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
Check the file for any unmatched #endif preprocessor directives. If you cannot find any such errors, scan the file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - unexpected EOF within #if.: The file scanner unexpectedly reached the end of the specified file within a #if-style preprocessor directive while it was processing symbols specified using the -D and/or -U options. The file may have been processed incorrectly, either scanning portions of the specified file that should not have been scanned, or not scanning portions that should have been.
Check the file for any #if-style preprocessor directives that do not have matching #endif directives or for any errors in the nesting of these directives. If you cannot find any such errors, scan the the file without using the -D and -U options. This causes the entire file to be scanned.

Warning: file filename, line line-number - unexpected EOLN within quoted text.: The file scanner unexpectedly detected the end of the specified line while processing a character or string literal within the specified file. The file was still scanned.
Check the specified file for any unmatched quotation marks. If there are any unmatched quotation mark errors, some underreporting or overreporting may occur because the file scanner handles the content of strings differently than other identifiers. This error is not displayed for script files since script file strings can span more than one line.

Warning: file filename, line line-number - unexpected EOF within quoted text.: The file scanner unexpectedly detected the end of the specified file while processing a character or string literal. The file is still scanned.
Check the specified file for any unmatched quotation marks. The file scanner cannot properly handle certain situations within script files, especially in scripts that are used to generate other scripts. If there are any unmatched quotation mark errors in a script file, some overreporting may occur because the file scanner does not strip comments within strings. This warning is only displayed for scripts and makefiles because strings cannot span more than one line for most programming languages.

Warning: file filename, line line-number - unexpected EOF within C comment.: The file scanner unexpectedly detected the end of the specified file while processing a C comment. The file is still scanned.
Correct any commenting errors in the specified file. Because the file scanner ignores comments, it may have ignored a significant portion of the file.

Warning: file filename, line line-number - nested C comment.: The file scanner detected a nested C comment within the specified file. The file is still scanned.
Correct any commenting errors in the specified file. Because the file scanner ignores comments, it may have ignored a significant portion of the file.

Warning: file filename, line line-number - unexpected EOF within braces {...}.: The file scanner unexpectedly detected the end of file before it processed one or more matching end braces. The file was still scanned. Missing braces may result in impacts on pointers to functions being missed.

Warning: file filename, line line-number - unexpected ending brace {...}.: The file scanner detected an ending brace when none was expected. The file was still scanned. Extra braces may result in impacts on pointers to functions being missed.

Your report is located in file report-filename: The file scanner has created a text-format output report that can be found in the specified file.

Use the following URL to access your report:report-URL: The file scanner has created an HTML-format output report that can be viewed in your web browser using the specified URL.

Printable version


Privacy statement	Using this site means you accept its terms	Feedback to DSPP

© 2007 Hewlett-Packard Development Company, L.P.