Application Verifier - Stop Codes - Webservices

The following stop codes are contained in this set of tests.

An invalid address of a Web Services Windows API intrinsic object was passed to the function

A call was made to a Web Services Windows API with an invalid object. The object referenced in parameter 1 may be invalid or have been already freed. To list the objects which have been created and freed, enter !avrf -ws -obj at the debugger prompt.

• Format: - Invalid address of a Web Services Windows API intrinsic object
• Parameter 1 - Address of object.
• Parameter 2 - Not used.
• Parameter 3 - Not used.
• Parameter 4 - Not used.

• Test Layer: Webservices
• Stop ID: INVALID_OBJECT_ADDRESS
• Stop code: 00006000
• Severity: Error
• One-time error: no
• Error report: Break
• Log to file: yes
• Create backtrace: yes

An operation in another thread is using a non-thread safe intrinsic Web Services Windows API object

Another thread is using a single threaded Web Services Windows API intrinsic object. To list the operations, and threads which are using the object, enter !avrf -ws -obj [object] at the debugger prompt, where [object] is the address of the single threaded intrinsic object.

• Format: - Multithreaded use of a Windows Web Services API intrinsic object
• Parameter 1 - Address of single threaded intrinsic object.
• Parameter 2 - Not used.
• Parameter 3 - Not used.
• Parameter 4 - Not used.

• Test Layer: Webservices
• Stop ID: SINGLE_THREADED_OBJECT_VIOLATION
• Stop code: 00006001
• Severity: Error
• One-time error: no
• Error report: Break
• Log to file: yes
• Create backtrace: yes

An intrinsic Web Services Windows API was freed when an asynchronous operation is still pending

An object is being freed while an asynchronous operation is still pending. To show the stack containing the operation still pending, enter !avrf -ws -obj [object] at the debugger prompt, where [object] is the address of the object still in use.

• Format: - Freeing of an object whilst still in use
• Parameter 1 - Address of intrinsic object.
• Parameter 2 - Not used.
• Parameter 3 - Not used.
• Parameter 4 - Not used.

• Test Layer: Webservices
• Stop ID: OBJECT_IN_USE
• Stop code: 00006002
• Severity: Error
• One-time error: no
• Error report: Break
• Log to file: yes
• Create backtrace: yes

A Web Services Windows API is taking too long to execute

An operation is taking too long to execute. To find out the operation, output the stack (using 'k') in the debugger.

• Format: - Web Services Windows API
• Parameter 1 - Not used.
• Parameter 2 - Not used.
• Parameter 3 - Not used.
• Parameter 4 - Not used.

• Test Layer: Webservices
• Stop ID: API_TIMEOUT
• Stop code: 00006003
• Severity: Warning
• One-time error: no
• Error report: Break
• Log to file: yes
• Create backtrace: yes

A corrupt WS_ASYNC_CONTEXT was passed into the callback function

A corrupt call context was passed into the callback function. This the result of memory corruption. To isolate this problem, re-run your application with heap checking enabled.

• Format: - A corrupt WS_ASYNC_CONTEXT was passed into the callback function
• Parameter 1 - Not used.
• Parameter 2 - Not used.
• Parameter 3 - Not used.
• Parameter 4 - Not used.

• Test Layer: Webservices
• Stop ID: CORRUPT_CALL_CONTEXT
• Stop code: 00006004
• Severity: Error
• One-time error: no
• Error report: Break
• Log to file: yes
• Create backtrace: yes

See Also

Application Verifier - Stop Codes and Definitions

Application Verifier - Overview

Application Verifier - Features

Application Verifier - Testing Applications

Application Verifier - Tests within Application Verifier

Application Verifier - Debugging Application Verifier Stops

Application Verifier - Frequently Asked Questions