How to access the call stack of a DOORS DXL script?

In order to write a proper assert(bool) function for testing my DXL programs, I would love to be able to print the call stack if the boolean is false.

Can anybody help me with either getting access to the call stack or finding a handy assertion function?

Solution

There really isn't a lot of information regarding this type of debugging available in DXL. I have seen some 3rd party DXL Compilers on the market (Sodius makes a good one) that might help or you can try to write your own debug using the information in the Error handling section of the DXL Reference Manual.

Assert struct vector length
"quiet" functions and assert condition
assert with formatted failure string
assert() function not showing up in disassembly
Checking if assertions are enabled
Validate specific date format in dbt
How to prevent Debug.Assert(...) to show a modal dialog
How to do a JUnit assert on a message in a logger
C++ Assumptions
Unit test project is not finding extension methods
c++ gtest print additional information in the end of a test when and only when the test fails
Contract.Assert do not throw compilation error
design of python: why is assert a statement and not a function?
Checking enum values at compile time
Unit Testing - How to Compare Two Paged Collections To Assert All Items Different?
Will an iterator surrounding an assert statement affect performance of production build?
rails assert_difference without specific difference value
What does the "assert" keyword do?
Python unittest - asserting dictionary with lists
What does this code mean: "assert result == repeat, (result, repeat)"?
PHPUnit: assert two arrays are equal, but order of elements not important
Assert in python3
Do compilers assume that "this" is not nullptr in debug mode?
static_assert vs C_ASSERT - which one to use?
Swift Assertions behaviour in production applications
Assert Success in Matlab Without Using Classes
IntelliJ, Junit 4 Maven - Cannot resolve symbol assertEquals
Jmeter: how to only perform last check once and only when first thread has completed all loops
How to get detailed assertion error messages from an external assertion function in pytest?
XSD: assert to check that values of several elements from same type are not equal