Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!mips!apple!portal!sv!usenet
From: moose (Michael Rutman)
Newsgroups: comp.sys.next
Subject: Re: How to you set a breakpoint to catch postscript errors
Message-ID: <1991May31.161911.3983@svc.portal.com>
Date: 31 May 91 16:19:11 GMT
References: <1011@nddsun1.sps.mot.com>
Sender: usenet@svc.portal.com
Reply-To: moose@sv.portal.com
Organization: Software Ventures Corporation.
Lines: 16
Nntp-Posting-Host: moose

In article <1011@nddsun1.sps.mot.com> leivian@axon.sps.mot.com (Bob Leivian)  
writes:
> I am getting errors from the DPS client ... offending command blah
> is printed into my terminal window but the program exits before telling
> me which of the two hundred PSlineto commands in my code that
> could have caused the problem.
> 

Run the program using -NXShowPS YES >largepsoutput
Then, using DisplayTalk from Adobe, step through the file largepsoutput until  
you find your error.
--
Michael Rutman				|	moose@svc.portal.com
Cubist					|	makes me a NeXT programmer
Software Ventures			|	For Your Eyes Only Public Key
smile, you're on standard disclaimer	|	071400171C051913