D
dbeavon
Guest
It will be good to start turning on these stacks. Now I'll immediately know where to look for a problem when my program execution encounters an error like so : ("** Invalid character in numeric input ?.") Unfortunately a vague data-related error message like that one might easily come from **any** part of our legacy ABL codebase. Errors like that one have been very hard to troubleshoot without call stacks. They are usually intermittent, so it is difficult to enable errorstack temporarily and capture one of them when you need it. If it wasn't because of performance concerns, then the only other reason I can think why errorstacks might have been disabled by default is so that OE ISVs can hide that level of information from their customers in the event of a bug. (IE. they may want to hide stacks for reasons that are similar to why they "encrypt" their ABL source files.) But hiding information has a cost in terms of maintenance and support. It may not be worth hiding stacks in those kinds situations either. We develop ABL for in house software and we certainly have no reason to hide call stacks. Thanks for all the help.
Continue reading...
Continue reading...