Sujet : Re: Show argument values in bgerror
De : donald.porter (at) *nospam* nist.gov (Don Porter)
Groupes : comp.lang.tclDate : 18. Sep 2024, 14:46:54
Autres entêtes
Organisation : ACMD ITL NIST
Message-ID : <vcelke$309g$1@dont-email.me>
References : 1
User-Agent : Mozilla Thunderbird
The [interp bgerror] command has been available since the release
of Tcl 8.5.0 in 2007. No one should be continuing to struggle against
the deficits of the [bgerror] facility.
On 9/17/24 17:31, alexandru wrote:
I have this ::bgerror function to help debug errors in program flow:
proc ::bgerror {message} {
global errorInfo
puts "*** START OF ERROR MESSAGE ***\n$message\n$errorInfo\n*** END OF
ERROR MESSAGE ***"
}
The issue is, that the errorInfo does not show the values of the
arguments of called procedures in the stack.
Thus it's often not clear which arguments lead the the error.
Is there a trick how to show the values with which the procedures were
called in the stack prior to the error?
Many thanks
Alexandru
-- | Don Porter Applied and Computational Mathematics Division || donald.porter@nist.gov Information Technology Laboratory || http://math.nist.gov/~DPorter/ NIST ||______________________________________________________________________|