Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: alexandru.dadalau@meshparts.de (alexandru)
Newsgroups: comp.lang.tcl
Subject: Show argument values in bgerror
Date: Tue, 17 Sep 2024 21:31:25 +0000
Organization: novaBBS
Message-ID: <b42edc7a9bab2a468f2694eda7a2df32@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="2448556"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="0Z5XV6kwM7Cos/IbgWfXZAYsazigEecpjCfqz3CX7rU";
User-Agent: Rocksolid Light
X-Rslight-Posting-User: 916f90664d3de2199c7a6231aba6924e4b1593d3
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Site: $2y$10$SQpjYn/Wmxyi8ayBJaoMyuZuEf2fV2fzTjMMJ95Dacv8om8Sl6sc2
Bytes: 1394
Lines: 15

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