L
Laura Stern
Guest
Rather than modify messages and do memory dumps, I would suggest that we just do what you've been alluding to all along - write the original message to the log file (for an AppServer) that caused the 14438 (along with the 14438). You can log a bug for this. And in general, if this comes from a thrown error object, the stack trace from the object should be output if -debugalert is on. This latter behavior SHOULD already be there, as that is what happens in the GUI version (i.e., the dialog from the Help button of the error alert box). If not, that is a bug. And yes, if your CATCH blocks are not for Progress.Lang.Error, they should be. Not sure why they wouldn't be already.
Continue reading...
Continue reading...