Bug 4723 - tlclient crashes under MS App Verifier (again)
: tlclient crashes under MS App Verifier (again)
Status: NEW
: ThinLinc
: trunk
: PC Unknown
: P2 Normal
: MediumPrio
Assigned To:
: 3936
  Show dependency treegraph
Reported: 2013-06-25 13:54 by
Modified: 2014-10-14 16:34 (History)
Acceptance Criteria:

Dr MinGW traceback of current source, debug build (7.34 KB, text/plain)
2013-06-25 13:55, Peter Åstrand


You need to log in before you can comment on or make changes to this bug.

Description From cendio 2013-06-25 13:54:26
This is bug 3936 again:

When using the MS App Verifier, tlclient crashes when opening the options

This seems to be a build system regression. If I back the tlclient source to
2012-10-25, the crash still happens.
------- Comment #1 From cendio 2013-06-25 13:55:25 -------
Created an attachment (id=480) [details]
Dr MinGW traceback of current source, debug build
------- Comment #2 From cendio 2013-11-04 12:46:58 -------
With build 4135, it's worse than 4.1.0: Now the client crashes also on every
login, if the "Handle" test is activated. This is the test description:

Handles Stop Details 

The Handles tests ensure that an application does not attempt to use invalid
handles. This includes the following checks: 

Ensures that handles are valid when passed to APIs that take a handle. If a
NULL value or an INVALID_HANDLE_VALUE value is passed, the handle is clearly
invalid and further investigation is necessary. 

Ensures that TLS indexes passed to TLS functions are valid. 

Ensures that APIs are not called with handles that have been closed. 

Following is a list of verifier stops that may occur when running the Handles
verifier against a solution or project on different platforms: 

Error message
 Stop code

Invalid handle exception for current stack trace

Invalid TLS index used in current stack

Invalid parameters for WaitForMultipleObjects call

NULL handle passed as parameter. A valid handle must be used

Waiting on a thread handle in DllMain

Incorrect object type for handle

There is one property that you can change for the Handles check:

Traces - Enter in the amount of handle traces to be saved. For example 1024
will save 1k handle traces.
------- Comment #3 From cendio 2014-10-14 16:34:00 -------
With 4.3.0, only the "Heaps" test causes the crash.