Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!cg-atla!bradlee
From: bradlee@cg-atla.UUCP (Rob Bradlee)
Newsgroups: comp.lang.postscript
Subject: Re: Alternatives to Adobe's ehandler.ps?
Keywords: errorhandler debugger
Message-ID: <9737@cg-atla.UUCP>
Date: 25 Apr 91 12:10:41 GMT
References: <9104231442.AA23295@cas.org> <1991Apr24.164156.29515@spool.cs.wisc.edu>
Reply-To: bradlee@cg-atla.UUCP (Rob Bradlee)
Organization: Agfa Compugraphic Division
Lines: 29

>
>From: fred@nada.kth.se (Fredric Ihren)
>For me debugging postscript has often involved the location problem -
>I know the error and the command, but _where_ in my file did it happen?
>Adobe's lib/ehandler.ps program for catching errors in Apple Laser Writers
>seems to be well known and used around the world.
>I have modified it slightly (with kind permission from Adobe) to make it
>present more information about the conditions when the error occurred, so that
>the _where_-problem mentioned above can be solved.

I'd just like to cast a vote in favor of this error handler.  I've used
it for the past year developing several PostScript procsets and it has
been invaluable.  I distribute it to all our test systems so that when
EQA has a problem I can download this, resend the file, and get a clear
picture of what went wrong.   It's a great alternative to LaserTalk
and 9 times out of 10 it tells you enough that you can see your error
right away.  You do need to know the password of the printer, however.





					Rob

-- 
Rob Bradlee  w:(508)-658-5600 X5153  h:(617)-944-5595
AGFA Compugraphic Division.    ...!{decvax,samsung}!cg-atla!bradlee
200 Ballardvale St.                        bradlee@cg-atla.agfa.com
Wilmington, Mass. 01887           The Nordic Way: Ski till it hurts!