Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
Forum Index » Server Platform » TSAPI SDK 8 crash after enable trace   XML
Author Message

Joined: 18/06/2019 08:24:47
Messages: 3


When we build our program with the sdk v8 : no errors (except for the missing keyword 'typedef' in the acs.h file from the sdk, but we fixed that on our own.)
- run it : it launches, but it doesn't seam to work. But it does not crash
- set the CSTATRACE env variable to enable the logs for the sdk.
- re-run our program : now it crashes instantly, and running it in gdb gives us the stack trace I provided. The file named after the value of CSTATRACE is created but it is empty.

Can you help me to resolve this problem please.

Joined: 20/06/2005 14:06:52
Messages: 862
Location: Thornton, CO

1) The level of assistance you will need here is not available to the free level of membership. Debugging assistance is provided to support enabled members:
2) no stack trace was provided
3) Do the sample applications provided with the SDK compile and run in your environment?
4) Can you make simple modifications to the sample apps, and get the CSTATRACE operational?

Joined: 18/06/2019 08:24:47
Messages: 3

Hello John,

Thank you for your response, I will test with sample application and i will update you.

Thanks a lot for your help.

Joined: 18/06/2019 08:24:47
Messages: 3


If we run the Avaya script application "tstest" the application works
If we activate the export of traces "CSTATRACE" and we launch "tstest"
we have a runtime error.

The client has a problem with his application he wants to launch
traces to debug but it is not possible, we have the message
"Segmentation fault (core dump), please see the screenshot of error image
message. please help us to resolve this issue.
For your information the customer has test his application with TSAPI
SDK 5 it work fine with AES8.


Joined: 09/01/2014 12:11:50
Messages: 96

The product team is aware of this issue, and are working on fix. Sorry, there are currently no workarounds or ETAs for when the fix will be provided.
Go to: