Hi Alex,
thank you for your code but I was asking more in-depth informations.
The Debugger can show the variables "active" for each "n", so that
with the call stack you can display the parameter values and the local
variables values (anche if compiled with -b you should be able also to
display var
francesco perillo wrote:
I now ask if is it possible to get a prg-level CallStack array in
order to use it in the errorsys handler.
I use:
function Stack2Str(n)
local cStackStr := ""
local cProcFile
DEFAULT n TO 2
while !empty(procname(n))
cStackStr += "Called from
In the debugger it is possible to see the CallStack and the variables
"active" in each stack level.
>From the debugger source code I see that the CallStack is passed to
__dbgEntry as a parameter and that parameter is built in C in funcyion
hb_dbgActivate( HB_DEBUGINFO *info ) where info is a pointe
