10-20-2013, 01:23 PM
Hello All,
great thread. If a future enhanced error logging functionality is in the works, it would be great if it somehow contained the callstack as well. It's sometimes hard to figure out which is the caller, thread entry function, and steps along the way in a complicated exe!
Thanks again,
S
great thread. If a future enhanced error logging functionality is in the works, it would be great if it somehow contained the callstack as well. It's sometimes hard to figure out which is the caller, thread entry function, and steps along the way in a complicated exe!
Thanks again,
S
Quote:GetCallStack [str*cs] [flags] ;;flags: 1 no code, 2 no formatting
QM 2.3.5.
Gets function call stack
It is a multiline list of function names. The first is current function, then its caller, caller's caller and so on.
cs - receives results. If omitted or 0, displays in QM output.
flags:
1 Get only function names. By default also gets current statement code. In exe never gets code.
2 Get plain text. By default the text is formatted for QM output.