Salesforce

Why is the CallStack property of an error object empty/null?

« Go Back

Information

 
TitleWhy is the CallStack property of an error object empty/null?
URL Name000041865
Article Number000162889
EnvironmentAll supported Operating Systems
OpenEdge 10.x
OpenEdge 11.x
Question/Problem Description
Why is the CallStack property of an error object empty/null?
What does the ERROR-STACK-TRACE attribute of the SESSION handle do? 
What does the -errorstack parameter do? 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Errors caught using structured error handling (a CATCH block or "ROUTINE-LEVEL ON ERROR UNDO, THROW") may be written to the client log by using the ERROR-STACK-TRACE and DEBUG-ALERT attributes of the SESSION handle

The CallStack will be empty/null if the ERROR-STACK-TRACE attribute of the SESSION handle is false and the -errorstack isn't used.

Set the ERROR-STACK-TRACE attribute to true or use the -errorstack parameter to have Error objects set their CallStack.

For further clarification refer to Article:
Workaround
Notes
References to other documentation:
OpenEdge Development: Error Handling, Chapter 6: "Using ABL Error Classes".
Keyword Phrase
Last Modified Date11/20/2020 7:35 AM

Powered by