I'm not familiar with TRAP, and could not find it in (an admittedly quick perusal of) the manuals. Is it a startup option, i.e. udt -TRAP, or a basic option?
I've been in places in the Unidata manual I've never seen before while researching this subject. And while the search for trapping runtime errors has thus far been fruitless, I DID run across the system command, udtbreakon, which seems to remove the only excuse we programmers had for continuing to enable the break in production; "what if there's a deadly embrace and we need to break one machine to allow the other to continue?" Still sifting thru the manuals here. I appreciate the response! Thanks, -- Dave Walker -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of john reid Sent: Friday, May 05, 2006 9:59 AM To: [email protected] Subject: Re: [U2] Runtime errors Failing a proper log file, is there the equivalent of the -TRAP run time break to debug when an error occurs? It might not be do-able in production environment but maybe for selected users. On 5/2/06, Dave Walker <[EMAIL PROTECTED]> wrote: > I'm sure we've all seen the user that ignores umpteen "WARNING: > UNINITIALIZED VARIABLE USED! Zero Assumed!" errors scrolling up their > screen. > > Is there a way to log non-fatal runtime errors so that they may be reviewed > later? Are they already logged someplace that I'm not aware of? I've checked > the various logs in /usr/ud/bin/saved_logs without finding what I'm looking > for. > > TIA, > -- > Dave Walker > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > -- john ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
